beads/docs/cli-reference/migrate-personal.md
Isis Anisoptera aadd21c40b docs(cli): move the graph plan schema into an embedded doc supplement
The --graph schema section was hand-written into the generated
docs/CLI_REFERENCE.md, which the byte-exact drift gate rejects and any
regeneration (including the docs-autofix bot) would erase — breaking
TestDocsGraphPlanExampleValidates. Long: strings can't carry it either:
escapeMDXText would mangle the fenced JSON example.

Add a command doc-supplement mechanism: raw Markdown embedded from
cmd/bd/help_supplements/ and appended after a command's flags by the docs
generator, so regeneration reproduces the section byte-for-byte in both
CLI_REFERENCE.md and the per-command create.md page. Document the
parent/estimate aliases and their precedence while moving the text.
Regeneration also restores the four per-command pages (heartbeat,
migrate-personal, reclaim, unclaim) that docs.json already listed but the
committed tree was missing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-18 11:52:57 -07:00

938 B

title description
bd migrate-personal Move personal planning issues from the project database to your planning repo

{/* AUTO-GENERATED: do not edit manually */}

Generated from bd help --doc migrate-personal.

Identify issues you created in the project database and move them to your personal planning repository (~/.beads-planning by default).

This is a one-time migration for contributors who created personal planning issues before contributor routing was configured.

The command:

  1. Finds all issues in the project database created by your git identity
  2. Shows you the list and asks for confirmation
  3. Moves them to the planning repo configured in routing.contributor

EXAMPLES: bd migrate-personal # Interactive: show list and prompt bd migrate-personal -y # Non-interactive: skip confirmation

bd migrate-personal [flags]

Flags:

  -y, --yes   Skip confirmation prompt