bd help --docs-root now additionally writes docs/cli-reference/ in Mintlify form (frontmatter title as H1, extensionless root-relative links, JSX auto-generated markers since Mintlify parses .md through MDX) and rewrites the CLI Reference pages array inside docs/docs.json via a textual splice that leaves the rest of the file byte-identical — the ~113 nav entries are never hand-maintained. The Docusaurus outputs (docs/CLI_REFERENCE.md, website/docs/cli-reference/, versioned snapshots) are unchanged. generate-cli-docs.sh --check seeds docs/docs.json and docs/cli-reference/ into its scratch root and diffs both; check-cli-docs-drift.sh adds them to GEN_PATHSPECS and the regeneration fingerprint; docs-autofix-push.sh allowlists the new generated paths; check-doc-flags.sh scans the new docs/ subdirectories and requires command coverage in docs/cli-reference/. Includes the initial docs/docs.json scaffold (nav mirrors the Docusaurus sidebar IA) and the generated docs/cli-reference/ pages. TDD: new emitter behavior covered in cmd/bd/help_all_test.go (Mintlify page format, nav splice correctness + idempotence, bare-root generation without docs.json).
49 lines
2 KiB
Markdown
49 lines
2 KiB
Markdown
---
|
|
title: "bd export"
|
|
description: "Export issues to JSONL format"
|
|
---
|
|
|
|
{/* AUTO-GENERATED: do not edit manually */}
|
|
|
|
Generated from `bd help --doc 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 exports
|
|
records from the issues table; it is not a full database backup and does not
|
|
capture Dolt branches, commit history, working-set state, or non-issue tables.
|
|
For supported full backup/restore flows, use 'bd backup init', 'bd backup sync',
|
|
and 'bd backup restore'.
|
|
|
|
By default, exports only regular issues (excluding infrastructure beads
|
|
like agents, 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 issues.jsonl # Export issues 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)
|
|
--exclude-owner stringArray Exclude issues created by this identity (repeatable; also reads export.exclude_owners config)
|
|
--include-infra Include infrastructure beads (agents, 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
|
|
--verbose Print filtered issue count when owners are excluded
|
|
```
|