mirror of
https://github.com/gastownhall/beads.git
synced 2026-09-14 20:17:24 +08:00
Chris Sells
d2f87d50de
* docs(pipeline): pin the generated CLI docs to the released bd; repair main's CLI reference The #4874 squash-merge raced the docs-autofix bot: the bot had pushed a regeneration from main's source onto the PR branch, so the squash landed a contradictory mix — the release-aligned hand-written docs plus a CLI reference re-documenting unreleased commands and flags, with docs.json referencing four pages (heartbeat, migrate-personal, reclaim, unclaim) whose files do not exist. That broken nav fails the docsync guard on main and on every branch cut from it. This restores the intended end state of #4874 and lands the pin that prevents the race from recurring. - Regenerate the CLI reference from a bd built from the v1.1.0 tag (CI's canonical pure-Go build), removing the unreleased commands/flags and fixing the dangling nav entries. - docs/cli-docs.pin names the release tag; scripts/resolve-docs-bd.sh builds and caches a canonical pure-Go bd from that tag, fetching the tag first in shallow CI checkouts. - generate-cli-docs.sh, check-doc-flags.sh, and check-cli-docs-drift.sh resolve bd through the pin and ignore a supplied binary while pinned (BD_DOCS_IGNORE_PIN=1 bypasses), so the drift gates and the autofix bot now enforce docs-match-release instead of docs-match-main. - tools/docsmint detects the pre-overhaul Docusaurus staging layout that bd <= v1.1.0 emits and converts it to the generic form before its normal Mintlify transform (tested); removable once the pin reaches a release whose emitter writes build/cli-docs. - check-doc-flags.sh: run without timeout(1) on macOS instead of failing Check 4. - Decision record: engdocs/decisions/2026-07-17-docs-release-pin.md; the beads-docs skill §8 updated to match. * lint: annotate gosec G705 false positive in the docsmint legacy bridge Same class as the existing nav-splice annotation: a developer tool writing repo Markdown, not a web-output sink.
33 lines
896 B
Markdown
33 lines
896 B
Markdown
---
|
|
title: "bd create-form"
|
|
description: "Create a new issue using an interactive terminal form."
|
|
---
|
|
|
|
{/* AUTO-GENERATED: do not edit manually */}
|
|
|
|
Generated from `bd help --doc create-form`.
|
|
|
|
Create a new issue using an interactive terminal form.
|
|
|
|
This command provides a user-friendly form interface for creating issues,
|
|
with fields for title, description, type, priority, labels, and more.
|
|
|
|
Use --parent to create a sub-issue under an existing parent issue.
|
|
The child will get an auto-generated hierarchical ID (e.g., parent-id.1).
|
|
|
|
The form uses keyboard navigation:
|
|
- Tab/Shift+Tab: Move between fields
|
|
- Enter: Submit the form (on the last field or submit button)
|
|
- Ctrl+C: Cancel and exit
|
|
- Arrow keys: Navigate within select fields
|
|
|
|
```
|
|
bd create-form [flags]
|
|
```
|
|
|
|
**Flags:**
|
|
|
|
```
|
|
--parent string Parent issue ID for creating a hierarchical child (e.g., 'bd-a3f8e9')
|
|
```
|