Three generated-content defects from the adversarial review, all structurally invisible to the drift gate (generated-vs-generated): - Usage lines now mirror Cobra's help template: a runnable command shows its UseLine, a command with subcommands shows '<path> [command]', both when both apply. Previously bare UseLine() stamped 'bd mol [flags]' on 30 parent pages — a line the binary never prints. - The generated CLI index publishes the Global Flags block; the binary prints it on every --help but no page carried it. - docsmint neutralizes prose lines that Mintlify's prebuild would dedent into MDX ESM blocks (a line beginning 'export'/'import' outside a fence gets wrapped in a code span). This is why /cli-reference/mail returned HTTP 200 while rendering only a parse-error placeholder — reproduced, fixed, and covered by a planted-hazard test; fenced content stays verbatim. Also rewords check-cli-docs-drift.sh's early-PASS message, which asserted 'the supplied binary differs' as the cause when uncommitted local edits produce the same result. All 113 pages + docs/CLI_REFERENCE.md regenerated through the pipeline; TDD'd in cmd/bd/help_all_test.go and tools/docsmint/docsmint_test.go. Verified live: /cli-reference/mail renders real content, zero parse errors; generate-cli-docs.sh --check, docsync, freshness, and mint broken-links all pass on this tree.
62 lines
2 KiB
Markdown
62 lines
2 KiB
Markdown
---
|
|
title: "bd graph"
|
|
description: "Display issue dependency graph"
|
|
---
|
|
|
|
{/* AUTO-GENERATED: do not edit manually */}
|
|
|
|
Generated from `bd help --doc graph`.
|
|
|
|
Display a visualization of an issue's dependency graph.
|
|
|
|
For epics, shows all children and their dependencies.
|
|
For regular issues, shows the issue and its direct dependencies.
|
|
|
|
With --all, shows all open issues grouped by connected component.
|
|
|
|
Display formats:
|
|
(default) DAG with columns and box-drawing edges (terminal-native)
|
|
--box ASCII boxes showing layers, more detailed
|
|
--compact Tree format, one line per issue, more scannable
|
|
--dot Graphviz DOT format (pipe to dot -Tsvg > graph.svg)
|
|
--html Self-contained interactive HTML with D3.js visualization
|
|
|
|
The graph shows execution order:
|
|
- Layer 0 / leftmost = no dependencies (can start immediately)
|
|
- Higher layers depend on lower layers
|
|
- Nodes in the same layer can run in parallel
|
|
|
|
Status icons: ○ open ◐ in_progress ● blocked ✓ closed ❄ deferred
|
|
|
|
Examples:
|
|
bd graph issue-id # Terminal DAG visualization (default)
|
|
bd graph --box issue-id # ASCII boxes with layer grouping
|
|
bd graph --dot issue-id | dot -Tsvg > graph.svg # SVG via Graphviz
|
|
bd graph --dot issue-id | dot -Tpng > graph.png # PNG via Graphviz
|
|
bd graph --html issue-id > graph.html # Interactive browser view
|
|
bd graph --all --html > all.html # All issues, interactive
|
|
|
|
```
|
|
bd graph [issue-id] [flags]
|
|
bd graph [command]
|
|
```
|
|
|
|
**Flags:**
|
|
|
|
```
|
|
--all Show graph for all open issues
|
|
--box ASCII boxes showing layers
|
|
--compact Tree format, one line per issue, more scannable
|
|
--dot Output Graphviz DOT format (pipe to: dot -Tsvg > graph.svg)
|
|
--html Output self-contained interactive HTML (redirect to file)
|
|
```
|
|
|
|
## bd graph check
|
|
|
|
Check the dependency graph for cycles, orphans, and other integrity issues.
|
|
|
|
Returns exit code 0 if the graph is clean, 1 if issues are found.
|
|
|
|
```
|
|
bd graph check [flags]
|
|
```
|