You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: Git-ignored directory paths are treated as unanchored patterns, excluding unrelated source files #2849
Thanks for the precise report and the suggested fix, @Victor-Rodriguez-Garcia! You were right: the folders git reports as ignored were added to the scope matcher as unanchored patterns, so the ignored root src/ hid every module's src/.
#2858 fixes it by matching those folders as exact paths from the project root, one step past anchoring them. The matcher library can't escape every character a folder name may contain (?, for example), so they're no longer read as patterns at all. The same change covers folders named like [draft] or scratch[1, which on 1.6.2 could match other folders or make the file watcher fail, and the includeIgnored entry codegraph init suggests for a gitignored nested repository.
Checked on real repos after writing what each project's local build writes at the root: every file git considers in scope is now indexed (your jib layout on a Maven project: 104 files before, 1,423 of 1,423 after), and nothing git ignores is added.
It's merged and ships in the next release. After upgrading, run codegraph index on the monorepo to pick up the Java files that were left out.
Activity
colbymchenry commentedon Oct 23, 2026
Thanks for the precise report and the suggested fix, @Victor-Rodriguez-Garcia! You were right: the folders git reports as ignored were added to the scope matcher as unanchored patterns, so the ignored root
src/hid every module'ssrc/.#2858 fixes it by matching those folders as exact paths from the project root, one step past anchoring them. The matcher library can't escape every character a folder name may contain (
?, for example), so they're no longer read as patterns at all. The same change covers folders named like[draft]orscratch[1, which on 1.6.2 could match other folders or make the file watcher fail, and theincludeIgnoredentrycodegraph initsuggests for a gitignored nested repository.Checked on real repos after writing what each project's local build writes at the root: every file git considers in scope is now indexed (your jib layout on a Maven project: 104 files before, 1,423 of 1,423 after), and nothing git ignores is added.
It's merged and ships in the next release. After upgrading, run
codegraph indexon the monorepo to pick up the Java files that were left out.fix(scope): a folder git ignores matches only itself, not every folde…
fix(rust): a folder git ignores matches only itself, not every folder…