Repository navigation
Add --prune flag to prune unrecognised files in generated dir - #42
Merged
Merged
Conversation
JamyGolden
requested review from
bezhermoso and
carmiac
and removed request for
a team
September 23, 2026 12:06
bezhermoso
reviewed
Sep 23, 2026
bezhermoso
left a comment
bezhermoso
left a comment
Member
There was a problem hiding this comment.
just have one nit, this looks good ❤️
JamyGolden
force-pushed
the
jamy/feature/prune-stale
branch
4 times, most recently
from
September 26, 2026 20:53
fcb9f8c to
327c4bd
Compare
JamyGolden
force-pushed
the
jamy/feature/prune-stale
branch
from
September 26, 2026 20:54
327c4bd to
ea5173d
Compare
JamyGolden
changed the title
--prune-stale flag to prune unrecognised files in generated dir--prune flag to prune unrecognised files in generated dir
bezhermoso
approved these changes
Sep 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding a
--prune-staleflag to the global tinted-theming automatic builds should fix this issue: tinted-theming/schemes#114 (comment)Change description
Add
build --prune-staleflag which deletes previously generated themes, or unknown files in out directory, of files that aren't recognised. Renaming a scheme previously left the old theme behind in every template repository indefinitely. Pruning is limited to files matching a template config entry's ownfilenamepattern, skips scheme systems that generated nothing in the same run, and only runs once every config entry has been generated successfully.