fix(customgitignore) parsing to respect repository boundaries #1859
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.
Fixes #209
Previously,
.gitignore
files from outside a Git repo - or from a parent repo - could be incorrectly applied.This led to unexpected exclusions in nested repository setups, such as submodules or vendored repos.
The updated logic includes proper detection of repository boundaries and support for symlink resolution to handle more complex project layouts.
Symlink resolution is fallback-safe and automatically skipped on unsupported platforms like Windows.
Changes included:
readIgnoreFilesFromParents
to stop traversal at repo boundariesisSubRepository
to detect nested repositoriesfilepath.EvalSymlinks
for more accurate path handlingparentPath
to resolve symlinked parent directoriesTests added:
.gitignore
leakage).gitignore
files applied)The docstring for
ParseGitIgnores
was also updated to reflect this behavior, without large structural changes.If you’d prefer the symlink logic to go in a follow-up PR, happy to split it. Thanks in advance for reviewing!
~ Pepijn