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).
27 lines
572 B
Markdown
27 lines
572 B
Markdown
---
|
|
title: "bd priority"
|
|
description: "Set the priority of an issue"
|
|
---
|
|
|
|
{/* AUTO-GENERATED: do not edit manually */}
|
|
|
|
Generated from `bd help --doc priority`.
|
|
|
|
Set the priority of an issue.
|
|
|
|
Shorthand for 'bd update <id> --priority <n>'.
|
|
|
|
Priority levels:
|
|
0 - Critical (security, data loss, broken builds)
|
|
1 - High (major features, important bugs)
|
|
2 - Medium (default)
|
|
3 - Low (polish, optimization)
|
|
4 - Backlog (future ideas)
|
|
|
|
Examples:
|
|
bd priority bd-123 0 # Critical
|
|
bd priority bd-123 2 # Medium
|
|
|
|
```
|
|
bd priority <id> <n> [flags]
|
|
```
|