Currently, claude-context respects ignore rules from .gitignore, but does not appear to respect ignore rules defined in .git/info/exclude.
.git/info/exclude is the standard Git mechanism for repository-local ignore rules that should not be committed. It is commonly used to exclude machine-specific files, local tooling artifacts, generated content, and other environment-specific files without exposing those details in the repository.
As a result, files intentionally excluded from the local repository can still be picked up by claude-context.
Please make claude-context honor .git/info/exclude in the same way it honors .gitignore.
Additionally, rather than manually parsing .gitignore files and related exclude rules, it may be more robust to delegate ignore resolution to Git itself. Git already provides commands such as git ls-files that can determine which files are tracked, untracked, or ignored while taking into account all relevant ignore sources (.gitignore, .git/info/exclude, global excludes, etc.). Using Git's own ignore machinery would help ensure behavior remains consistent with the repository's actual Git configuration.
Currently, claude-context respects ignore rules from .gitignore, but does not appear to respect ignore rules defined in .git/info/exclude.
.git/info/exclude is the standard Git mechanism for repository-local ignore rules that should not be committed. It is commonly used to exclude machine-specific files, local tooling artifacts, generated content, and other environment-specific files without exposing those details in the repository.
As a result, files intentionally excluded from the local repository can still be picked up by claude-context.
Please make claude-context honor .git/info/exclude in the same way it honors .gitignore.
Additionally, rather than manually parsing .gitignore files and related exclude rules, it may be more robust to delegate ignore resolution to Git itself. Git already provides commands such as git ls-files that can determine which files are tracked, untracked, or ignored while taking into account all relevant ignore sources (.gitignore, .git/info/exclude, global excludes, etc.). Using Git's own ignore machinery would help ensure behavior remains consistent with the repository's actual Git configuration.