🐛 Repo Watch: drop stale/unreadable worktrees (kill SCAN ERR)#210
Merged
Conversation
`git worktree list` keeps registrations for worktrees in ephemeral locations (/tmp, ~/Library/Caches/codex-builds) long after their directories are deleted. Scanning them failed with "Could not read Git status", surfacing as SCAN ERR rows that also pushed their project to an "attention" state — pure noise. Now skip any worktree the scan can't read, and drop projects left with no readable worktrees. No signal lost (an unreadable worktree carries none).
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repo Watch was showing SCAN ERR rows for worktrees in ephemeral paths (
/tmp,~/Library/Caches/codex-builds) whose directories had been deleted —git worktree liststill registers them, the scan hits "Could not read Git status", and the bogus error even bumped the parent project to an attention state.Fix: skip worktrees the scan can't read, and drop projects left with zero readable worktrees. An unreadable worktree carries no signal, so nothing useful is lost.
Verified: with the same discovery hints that previously produced 3 SCAN ERR rows, the snapshot now returns 0 errored worktrees (and
actiondrops from attention → active). Typecheck clean; repo-watch tests 6/6.