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(detect_changes): impacted_symbols always empty for projects inside git worktrees #690
detect_changes returns an empty impacted_symbols array for projects that reside inside git worktrees. The change detection itself may work (detecting which files changed), but the downstream symbol-impact analysis fails to resolve the symbols.
Possible cause
Git worktrees have a .git file instead of a .git/ directory. If the change detector resolves the git dir by reading the worktree pointer but the symbol resolver treats .git as a regular directory, the git metadata lookup fails silently and returns empty results.
Thanks for raising this! It looks like a duplicate of an existing issue — the canonical one is linked above. Continuing the discussion there keeps everything in one place. We leave this open for visibility; a maintainer will close it once it's fully covered.
Thanks for writing this up. This duplicates #659, which is the canonical detect_changes worktree impacted-symbols issue. The corresponding fix PR is #672, so I am closing this duplicate and keeping status on the canonical tracker.
Activity
fix(git): resolve canonical_root '..' components in worktree git_comm…
fix(git): resolve canonical_root '..' components in worktree git_comm…
fix(git): resolve canonical_root '..' components in worktree git_comm…
github-actions commentedon Jul 1, 2026
Thanks for raising this! It looks like a duplicate of an existing issue — the canonical one is linked above. Continuing the discussion there keeps everything in one place. We leave this open for visibility; a maintainer will close it once it's fully covered.
DeusData commentedon Jul 1, 2026
Thanks for writing this up. This duplicates #659, which is the canonical
detect_changesworktree impacted-symbols issue. The corresponding fix PR is #672, so I am closing this duplicate and keeping status on the canonical tracker.