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
fix(core): .boltignore root-anchored patterns misresolve for subdirectory searches #93
Follow-up to #86 / #87 (review findings on the merged PR).
Ripgrep search spawns rg with the requested search directory as the process cwd, and rg resolves --ignore-file patterns relative to that cwd. A root-level .boltignore rule like /src/generated/ therefore matches the wrong path when grep/glob/find run from a subdirectory, so the files it should hide leak into agent search results. The child-to-root --ignore-file argument order also gave parent files higher precedence than nearer ones.
Additionally, the HTTP file.list handler turns any .boltignore read failure into an empty policy (exposing files the policy should hide) and applies .boltignore with a different precedence than the ripgrep path.
Fix: treat .boltignore as repository-root-only, run rg from the repo root (confining the walk to the requested directory and re-basing globs/output paths) so root-anchored rules keep their scope, only treat a missing .boltignore as an empty policy in file.list, and align its precedence with rg's lowest-priority --ignore-file semantics.
Activity