This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

Renaming abcd's home from ~/.abcd to ~/.abcd.noindex, as the noindex stop tells the person to (mv ~/.abcd ~/.abcd.noindex), moves every git worktree kept in the store under it, and git records a worktree's location in absolute form: after the move each repository lists those worktrees as prunable ('gitdir file points to non-existent location'), and a git worktree prune, by hand or by a tool, deletes their links. Reproduced on a scratch repository 2026-10-04: after mv, git worktree list marks the moved worktree prunable; git -C <moved worktree> worktree repair restores it. spc-2610031309233367 neither names this nor tells the person, and on the product thinker's machine the store holds about thirty live session worktrees.

issueresolvedmajoriss-2610040147016103

Renaming abcd's home from ~/.abcd to ~/.abcd.noindex, as the noindex stop tells the person to (mv ~/.abcd ~/.abcd.noindex), moves every git worktree kept in the store under it, and git records a worktree's location in absolute form: after the move each repository lists those worktrees as prunable ('gitdir file points to non-existent location'), and a git worktree prune, by hand or by a tool, deletes their links. Reproduced on a scratch repository 2026-10-04: after mv, git worktree list marks the moved worktree prunable; git -C <moved worktree> worktree repair restores it. spc-2610031309233367 neither names this nor tells the person, and on the product thinker's machine the store holds about thirty live session worktrees.

Grounds

  • pursued: a person who renames ~/.abcd as the stop says and runs the printed loop finds every store worktree listed again by its repository and none prunable; a moved worktree still listed prunable after the loop would show it wrong

Frontmatter

idiss-2610040147016103
typeissue
lifecycleresolved
severitymajor

mentions2