Repository navigation
Stranded worktree: research-provider-quota-headroom has held unsaved work for 11 days #15839
Description
Activity
👋 Auto-triage could not confidently classify this issue (no confident signal). Could a maintainer add the appropriate labels (
frontend,backend,infrastructure,docs,testingandgood-first-issue,intermediate,advanced)?Closing as a false alarm — zero work at risk.
git diff --shortstaton that worktree: 43 files changed, 0 insertions(+), 0 deletions(-). Every one of the 43 is a mode-bit change. There is no content to preserve, so there is nothing to commit and nothing to lose.Its PR #15033 was closed unmerged, so the branch itself is a separate decision, but this issue's premise — unsaved work sitting on one disk — does not hold.
Root cause, now fixed: the escalation used
git status --porcelain | wc -l, which counts paths differing in any way including permission bits. The reaper now measures content changes viadiff --numstatand classifies a tree whose dirt is entirely mode bits as NOISE, which is not escalated at all.
A worktree has held unsaved work for 11 days with no activity. It is not
reapable and never will be on its own: the reaper only retires work that is
safe on the remote, so this is skipped on every run and would otherwise stay
invisible indefinitely.
This is not a request to delete anything. The work may be worth finishing,
and nothing here has judged that. It is filed so it stops being invisible.
research-provider-quota-headroomProvenance
A worktree goes quiet for reasons that leave no trace either way, so this is
work to resume rather than a decision someone deferred. Do not infer intent from
the silence.
What to do
git worktree add .worktrees/research-provider-quota-headroom research-provider-quota-headroom