Skip to content

fix(indexer): exclude nested .remote-git dirs during /work multi-repo…#58

Merged
m1rl0k merged 2 commits into
Context-Engine-AI:testfrom
voarsh2:commit-gitremote-index-ignore
Dec 15, 2025
Merged

fix(indexer): exclude nested .remote-git dirs during /work multi-repo…#58
m1rl0k merged 2 commits into
Context-Engine-AI:testfrom
voarsh2:commit-gitremote-index-ignore

Conversation

@voarsh2

@voarsh2 voarsh2 commented Dec 13, 2025

Copy link
Copy Markdown
Contributor

… scans

When indexing /work in dev-remote, repos live under /work//..., so the default dir exclude "/.remote-git" did not prune nested ".remote-git" folders. This caused git_history_*.json manifests to be indexed as code.

Treat root-style single-segment exclude prefixes (e.g. "/.remote-git", "/.git") as "exclude-by-basename anywhere" to correctly prune nested repo metadata dirs. Add a regression test for /repo/.remote-git exclusion.

… scans

When indexing /work in dev-remote, repos live under /work/<repo>/..., so the
default dir exclude "/.remote-git" did not prune nested ".remote-git" folders.
This caused git_history_*.json manifests to be indexed as code.

Treat root-style single-segment exclude prefixes (e.g. "/.remote-git", "/.git")
as "exclude-by-basename anywhere" to correctly prune nested repo metadata dirs.
Add a regression test for /repo/.remote-git exclusion.
Replace derived "exclude by basename  anywhere" behavior with an explicit allowlist of directory names (.git, .remote-git, .codebase, node_modules).

Keeps dist/build root-relative while making multi-repo /work scans prune nested repo metadata dirs without surprising side effects.
@voarsh2 voarsh2 marked this pull request as ready for review December 15, 2025 00:31
@m1rl0k m1rl0k merged commit 04a92c4 into Context-Engine-AI:test Dec 15, 2025
1 check passed
@voarsh2 voarsh2 deleted the commit-gitremote-index-ignore branch December 16, 2025 06:21
m1rl0k added a commit that referenced this pull request Mar 1, 2026
fix(indexer): exclude nested .remote-git dirs during /work multi-repo…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants