Skip to content
This repository has been archived by the owner on Nov 4, 2023. It is now read-only.

Rename custom.css #564

Closed
chadmccune opened this issue Dec 1, 2020 · 1 comment · Fixed by #636
Closed

Rename custom.css #564

chadmccune opened this issue Dec 1, 2020 · 1 comment · Fixed by #636

Comments

@chadmccune
Copy link

IMHO, custom.css should either be removed from the release packages or renamed. This would make upgrading easier. Since custom.css is empty by default, this at worst would cause unseen 404's, and at best prevent someone from accidentally overwriting their custom css file when upgrading.
rchl added a commit that referenced this issue Feb 15, 2021
@rchl
fix: don't include empty custom.css in the release
d038e04 
Resolves #564
@rchl rchl mentioned this issue Feb 15, 2021
Merged
@rchl
Copy link
Collaborator

rchl commented Feb 15, 2021 •
edited
Loading

Good point. Created PR to fix that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: don't include empty custom.css in the release resoai/TileBoard
2 participants
@rchl @chadmccune