Open
Conversation
ctron
approved these changes
Apr 22, 2025
Collaborator
ctron
left a comment
There was a problem hiding this comment.
Sounds reasonable and looks good to me.
Might be cool to have a list instead of "or".
Author
|
Something like this? if [STAGE_DIR, ".git"].iter().any(|s| entry.file_name() == *s) {
continue;
}I also tried using if [STAGE_DIR, ".git"].contains(&&*entry.file_name().to_string_lossy()) {
continue;
}I feel like the "or" is a little more readable than either of these, but there might be a better way that what I have here. |
Collaborator
|
I though about adding a const list, and the using that list. So that, later on, that can easily be extended. |
Contributor
|
what about having something (sketched) like this in #[arg(short, long, env = "TRUNK_CLEAN_PRESERVE_FILES")]
pub preserve_files: Option<Vec<String>> |
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.
When cleaning the dist directory before moving build artifacts from the staging area, if a .git file exists, it should not be removed. This allows Trunk to build into a git worktree, for example.
This behavior also exists in Vite which was introduced in this PR. Part of their justification is that a .git file could not be generated by Vite, but I'm not sure if this invariant holds for Trunk.