Why: #4365 reports two documented CLI affordances that either fail or require a second command. children advertised --pretty but rejected it, and defer had no way to capture the reason at deferral time. What: add the children --pretty flag by delegating to list's existing tree renderer, add defer --reason by appending to notes during the status update, and refresh generated CLI docs. Agent-Signature: codex-unknown-model-unknown-reasoning on behalf of matt wilkie
37 lines
1 KiB
Markdown
37 lines
1 KiB
Markdown
---
|
|
id: defer
|
|
title: bd defer
|
|
slug: /cli-reference/defer
|
|
sidebar_position: 999
|
|
---
|
|
|
|
<!-- AUTO-GENERATED: do not edit manually -->
|
|
Generated from `bd help --doc defer`
|
|
|
|
## bd defer
|
|
|
|
Defer issues to put them on ice for later.
|
|
|
|
Deferred issues are deliberately set aside - not blocked by anything specific,
|
|
just postponed for future consideration. Unlike blocked issues, there's no
|
|
dependency keeping them from being worked. Unlike closed issues, they will
|
|
be revisited.
|
|
|
|
Deferred issues don't show in 'bd ready' but remain visible in 'bd list'.
|
|
|
|
Examples:
|
|
bd defer bd-abc # Defer a single issue (status-based)
|
|
bd defer bd-abc --until=tomorrow # Defer until specific time
|
|
bd defer bd-abc --reason="waiting on API access"
|
|
bd defer bd-abc bd-def # Defer multiple issues
|
|
|
|
```
|
|
bd defer [id...] [flags]
|
|
```
|
|
|
|
**Flags:**
|
|
|
|
```
|
|
--reason string Record why this issue is being deferred (appended to notes)
|
|
--until string Defer until specific time (e.g., +1h, tomorrow, next monday)
|
|
```
|