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).
28 lines
713 B
Markdown
28 lines
713 B
Markdown
---
|
|
title: "bd link"
|
|
description: "Link two issues with a dependency"
|
|
---
|
|
|
|
{/* AUTO-GENERATED: do not edit manually */}
|
|
|
|
Generated from `bd help --doc link`.
|
|
|
|
Link two issues with a dependency.
|
|
|
|
Shorthand for 'bd dep add <id1> <id2>'. By default creates a "blocks"
|
|
dependency (id2 blocks id1). Use --type to specify a different relationship.
|
|
|
|
Examples:
|
|
bd link bd-123 bd-456 # bd-456 blocks bd-123
|
|
bd link bd-123 bd-456 --type related # bd-123 related to bd-456
|
|
bd link bd-123 bd-456 --type parent-child
|
|
|
|
```
|
|
bd link <id1> <id2> [flags]
|
|
```
|
|
|
|
**Flags:**
|
|
|
|
```
|
|
-t, --type string Dependency type (blocks|tracks|related|parent-child|discovered-from) (default "blocks")
|
|
```
|