Block rename-prefix from running in git worktrees#1792
Merged
steveyegge merged 1 commit intosteveyegge:mainfrom Feb 16, 2026
Merged
Block rename-prefix from running in git worktrees#1792steveyegge merged 1 commit intosteveyegge:mainfrom
steveyegge merged 1 commit intosteveyegge:mainfrom
Conversation
…teveyegge#1645) Co-Authored-By: Claude Opus 4.6 <[email protected]>
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
2 participants
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.
Summary
Block
bd rename-prefixfrom running inside git worktrees, where it would export renamed issues to the main worktree's JSONL file, leaving the current worktree's JSONL stale.Fixes #1645
Changes Made
rename_prefix.go— detects worktree at command start and exits with a helpful error directing users to run from the main repositoryinit.go:168-186which blocksbd initin worktreesBackward Compatibility
✅ Maintained: Only adds a guard for an unsupported scenario that previously produced incorrect results
✅ Same behavior: Running from main repository works exactly as before
Technical Details
findJSONLPath()always resolves to the main worktree's JSONL becausebeads.dbonly exists there. Runningrename-prefixfrom a worktree would rename issues in the shared DB and export to the main worktree's JSONL, leaving the current worktree's JSONL with stale (old-prefix) issue IDs. The fix blocks this at the command level with a clear error message.Size: Small ✓
🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.6 [email protected]