* docs: generate CLI reference from live help * docs(cli): move bd version stamp from per-command pages to index only Drops the `(bd version X.Y.Z)` suffix from the auto-generated header on every per-command CLI reference page (writeSingleCommandDoc) and the docs/CLI_REFERENCE.md preamble (writeAllHelp). The version label now lives only on the index page emitted by scripts/generate-cli-docs.sh: - Dev tree (website/docs/cli-reference/index.md, docs/CLI_REFERENCE.md): labelled "Latest" - Versioned snapshots (website/versioned_docs/version-X.Y.Z/...): labelled with the explicit semver tag parsed from the directory name This eliminates the 100+-file no-signal diff a release version bump otherwise produces, restoring the "regen as a separate small commit" workflow PR #3704 enables. After this change a version bump alone yields zero diff on the dev tree; only the new versioned snapshot created at release-cut time carries the new tag. No datestamps are introduced anywhere — scripts/generate-cli-docs.sh --check remains deterministic across CI runs. Refs: mybd-afb, PR #3704 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: CI Bot <ci@beads.test> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
78 lines
2.5 KiB
Markdown
78 lines
2.5 KiB
Markdown
---
|
|
id: init-safety
|
|
title: bd init-safety
|
|
slug: /cli-reference/init-safety
|
|
sidebar_position: 999
|
|
---
|
|
|
|
<!-- AUTO-GENERATED: do not edit manually -->
|
|
Generated from `bd help --doc init-safety`
|
|
|
|
## bd init-safety
|
|
|
|
bd init flag safety contract.
|
|
|
|
Every bd init invocation resolves project_id from exactly one explicitly
|
|
named source (local reinit, remote adoption, or a fresh mint). When the
|
|
source is ambiguous, bd init refuses.
|
|
|
|
FLAG SURFACE
|
|
|
|
bd init Mint a new identity. Bootstraps from
|
|
origin if it has refs/dolt/data.
|
|
|
|
bd init --reinit-local Re-initialize local .beads/ over existing
|
|
local data. Does NOT authorize discarding
|
|
remote history. If origin has Dolt data
|
|
this will refuse — pair with
|
|
--discard-remote to override.
|
|
|
|
bd init --reinit-local \ Discard the remote's Dolt history and
|
|
--discard-remote replace it with the local reinit. First
|
|
bd dolt push after this will be a
|
|
history-replacing force-push.
|
|
|
|
bd init --force Deprecated alias for --reinit-local.
|
|
Kept working for ≥2 releases.
|
|
|
|
ADOPTING A REMOTE
|
|
|
|
If you want to use the remote's existing history, use:
|
|
|
|
bd bootstrap
|
|
|
|
bd init will automatically suggest this when a remote is detected.
|
|
|
|
DESTROY-TOKEN (non-interactive only)
|
|
|
|
When running with no TTY (CI, agents, piped input), --discard-remote
|
|
requires an explicit --destroy-token value. The token format is:
|
|
|
|
DESTROY-<issue-prefix>
|
|
|
|
For example, if your issue prefix is "bd", the token is "DESTROY-bd":
|
|
|
|
bd init --reinit-local --discard-remote --destroy-token=DESTROY-bd
|
|
|
|
In interactive (TTY) mode you confirm via a typed prompt instead. The
|
|
token is not echoed by bd's runtime error messages — this is a
|
|
deliberate guard against pattern-matched one-liners (see
|
|
docs/adr/0002-init-safety-invariants.md).
|
|
|
|
EXIT CODES
|
|
|
|
10 refused: remote has Dolt history and you passed --force/--reinit-local
|
|
without --discard-remote
|
|
11 refused: existing local data and you declined the destroy confirm
|
|
12 refused: --discard-remote passed without a valid --destroy-token
|
|
(non-interactive mode)
|
|
|
|
RECOVERY
|
|
|
|
If you hit a refusal, see docs/RECOVERY.md for step-by-step recovery
|
|
playbooks for each exit code.
|
|
|
|
|
|
```
|
|
bd init-safety
|
|
```
|