fix: close --quiet bypass in bd init --force safety guard#2802
Merged
steveyegge merged 1 commit intosteveyegge:mainfrom Mar 27, 2026
Merged
fix: close --quiet bypass in bd init --force safety guard#2802steveyegge merged 1 commit intosteveyegge:mainfrom
steveyegge merged 1 commit intosteveyegge:mainfrom
Conversation
Contributor
Author
|
i think this is the wrong fix; beads should not know about gas town. the confirm destroy i'm not against though |
quad341
force-pushed
the
fix/init-force-guard
branch
2 times, most recently
from
8e67aa5 to
f34e9c6
Compare
quad341
changed the title
3 tasks
Contributor
Author
|
Note: v0.62 is a breaking release over v0.61 that drops Gas Town knowledge from beads. This PR is part of that effort — the |
Contributor
Author
|
this has all of my other changes also merged into it. silly claude |
--force --quiet previously printed a warning but continued anyway, silently destroying the database. Now it refuses like the default non-interactive path and requires --destroy-token to proceed. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
quad341
force-pushed
the
fix/init-force-guard
branch
from
f34e9c6 to
fd55508
Compare
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
bd init --force --quietpreviously printed a warning but continued anyway, silently destroying the database--destroy-token=DESTROY-<prefix>to proceed--quietspecial case that bypassed the safety guardThis is the root cause of two data loss incidents where
bd init --forcedestroyed rig identity beads, agent state, and issue history.Test plan
go build ./...compiles cleanbd init --force --quietin a repo with issues → refuses (was: silent destruction)bd init --force --destroy-token=DESTROY-<prefix>→ proceeds as beforebd init --forcein interactive terminal → prompts "Type 'destroy N issues'" as before🤖 Generated with Claude Code