Repository navigation
Exclude directories containing CACHEDIR.TAG - #845
Merged
Merged
Conversation
SimonCropp
changed the title
Closed
5 tasks done
This was referenced Sep 24, 2026
Merged
Merged
This was referenced Sep 24, 2026
Open
6 tasks done
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
1 participant
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.
Skips any directory that contains a
CACHEDIR.TAGfile (Cache Directory Tagging spec), inDefaultDirectoryExclusions.Cargo writes one into its
targetdirectory (whatever it is named, including a customCARGO_TARGET_DIR). Scanning that directory is wasted work and can fail outright: it holds files cargo keeps byte-range locked (e.g..cargo-artifact-lock), and when two projects in one solution reference MarkdownSnippets their concurrent scans fail with "another process has locked a portion of the file". krillaNet currently works around this with"ExcludeDirectories": [ "target" ].Keyed on the marker rather than the name
target, which is too generic to exclude outright. Other tools that follow the spec get skipped too.