* fix(close): support per-id reasons Why: upstream GH#3279 reports repeated --reason values applying incorrectly across multi-ID close, while GH#3268 needs a ready zero-dependency regression guard to prevent queue drift. _codex-gpt-5.5-medium on behalf of matt wilkie_ * docs: refresh close CLI references _codex-gpt-5.5-medium on behalf of CI Bot_ * fix(close): preserve empty reason compatibility Ignore empty --reason occurrences so explicit empty strings continue to fall back to the default close reason and do not conflict with --reason-file. Clarify that repeated reasons map to IDs by positional index. _codex-gpt-5.5-medium on behalf of matt wilkie_
1.2 KiB
1.2 KiB
| id | title | slug | sidebar_position |
|---|---|---|---|
| close | bd close | /cli-reference/close | 60 |
Generated from bd help --doc close
bd close
Close one or more issues.
If no issue ID is provided, closes the last touched issue (from most recent create, update, show, or close operation).
When closing multiple issues, provide one --reason for all IDs or repeat --reason once per ID. Reasons map positionally: the first --reason applies to the first ID, the second --reason to the second ID, regardless of where the flags appear in the command line.
bd close [id...] [flags]
Aliases: done
Flags:
--claim-next Automatically claim the next highest priority available issue
--continue Auto-advance to next step in molecule
-f, --force Force close pinned issues or unsatisfied gates
--no-auto With --continue, show next step but don't claim it
-r, --reason string Reason for closing
--reason-file string Read close reason from file (use - for stdin)
--session string Claude Code session ID (or set CLAUDE_SESSION_ID env var)
--suggest-next Show newly unblocked issues after closing