* 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>
49 lines
1.7 KiB
Markdown
49 lines
1.7 KiB
Markdown
---
|
|
id: export
|
|
title: bd export
|
|
slug: /cli-reference/export
|
|
sidebar_position: 220
|
|
---
|
|
|
|
<!-- AUTO-GENERATED: do not edit manually -->
|
|
Generated from `bd help --doc export`
|
|
|
|
## bd export
|
|
|
|
Export all issues to JSONL (newline-delimited JSON) format.
|
|
|
|
Each line is a complete JSON object representing one issue, including its
|
|
labels, dependencies, and comments.
|
|
|
|
This command is for issue export, migration, and interoperability. It does
|
|
not produce the JSONL backup snapshot used by 'bd backup restore'. For
|
|
supported backup/restore flows, use 'bd backup', 'bd backup export-git',
|
|
and 'bd backup restore'.
|
|
|
|
By default, exports only regular issues (excluding infrastructure beads
|
|
like agents, rigs, roles, and messages). Use --all to include everything.
|
|
|
|
Memories (from 'bd remember') are excluded by default because they may
|
|
contain sensitive agent context. Use --include-memories or --all to
|
|
include them.
|
|
|
|
EXAMPLES:
|
|
bd export # Export issues to stdout
|
|
bd export -o backup.jsonl # Export to file
|
|
bd export --include-memories # Export issues + memories
|
|
bd export --all -o full.jsonl # Include infra + templates + gates + memories
|
|
bd export --scrub -o clean.jsonl # Exclude test/pollution records
|
|
|
|
```
|
|
bd export [flags]
|
|
```
|
|
|
|
**Flags:**
|
|
|
|
```
|
|
--all Include all records (infra, templates, gates, memories)
|
|
--include-infra Include infrastructure beads (agents, rigs, roles, messages)
|
|
--include-memories Include persistent memories (from 'bd remember') in the export
|
|
-o, --output string Output file path (default: stdout)
|
|
--scrub Exclude test/pollution records
|
|
```
|