chore: ignore the Beadhive per-session gate lock - #480
Merged
Conversation
`bh hive sync` refuses to sync a hive whose working tree is dirty. bh writes `.beads.gate.lock` at the repo root every session; untracked, it made the tree permanently dirty, so this hive was skipped on every sync run. phaze already carried this rule, which is why phaze was the only hive that synced. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K9qDLFXgqBe3JviJS5oLdM
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
E2E Coverage (chromium)
|
Contributor
E2E Coverage (firefox)
|
Contributor
E2E Coverage (webkit)
|
Contributor
E2E Coverage (webkit - iPad Pro 11)
|
Contributor
E2E Coverage (webkit - iPhone 15)
|
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.
bh hive syncrefuses to sync a hive whose git working tree is dirty. Beadhive writes.beads.gate.lockat the repo root every session; because it was untracked and unignored, the tree was permanently dirty and this hive was skipped on every sync run.Verified today: of the four registered hives,
phazewas the only one that synced — and the only one already carrying this ignore rule (phaze/.gitignore). The other three each failed withdirty branch(es): main.It also adds
/.codex/, which was untracked here for the same reason.Rule is root-anchored, matching the phaze convention, since bh writes the file at the repo root and nowhere else.
🤖 Generated with Claude Code
https://claude.ai/code/session_01K9qDLFXgqBe3JviJS5oLdM