Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as opaque submodule gitlinks on GitHub) into fully-tracked first-party content. AITM now merges its 7 vendored repos as first-party engines: - memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts - git: vendored C git (bundled binary) + gitnexus (in-process code intelligence) - agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess) Includes the full session's product build: Gitgram web/mobile/backend features, AITM website/CLI/MCP, the unified memory layer, engine build tooling (scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md), and extensive test suites. Build artifacts, node_modules, external/, and gemini-cli are gitignored. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
967 B
id, title, slug, sidebar_position
| id | title | slug | sidebar_position |
|---|---|---|---|
| statuses | bd statuses | /cli-reference/statuses | 999 |
Generated from bd help --doc statuses
bd statuses
List all valid issue statuses and their categories.
Built-in statuses (open, in_progress, blocked, etc.) are always valid. Additional statuses can be configured via status.custom:
bd config set status.custom "in_review:active,qa_testing:wip,on_hold:frozen"
Categories control behavior: active — appears in 'bd ready' and default 'bd list' wip — excluded from 'bd ready', visible in default 'bd list' done — excluded from 'bd ready' and default 'bd list' frozen — excluded from 'bd ready' and default 'bd list'
Statuses without a category (legacy format) are valid but excluded from 'bd ready'.
Examples: bd statuses # List all statuses with icons and categories bd statuses --json # Output as JSON
bd statuses