issue close: leave a closing comment with -c/--comment or -F #22

Closed
opened 2026-10-14 14:39:09 -05:00 by jeff · 0 comments
Owner

Reported by harrier, which is moving its issue workflow from fj to zfj.

What

zfj issue close <n> -c <text> (and -F <file>, - for stdin) posts the comment, then closes the issue — the convention of closing with a word on why, in one command rather than issue comment followed by issue close.

Decided

  • The comment goes first, then the close: if the close fails, the reason is on the issue and running it again is harmless apart from a second comment; the other order leaves a closed issue with no explanation.
  • -c is fj's spelling and gh's (gh issue close -c). -F reads a file, as for comment. No editor is opened: without either flag, close closes with no comment, as now.
  • If the comment fails, the issue is not closed.

Done when

issue close <n> -c "..." leaves the comment on the issue and the issue closed; the VM test checks it, and docs/agents/issue-tracker.md's Close line says to use it.

Reported by harrier, which is moving its issue workflow from fj to zfj. ## What `zfj issue close <n> -c <text>` (and `-F <file>`, `-` for stdin) posts the comment, then closes the issue — the convention of closing with a word on why, in one command rather than `issue comment` followed by `issue close`. ## Decided - The comment goes first, then the close: if the close fails, the reason is on the issue and running it again is harmless apart from a second comment; the other order leaves a closed issue with no explanation. - `-c` is fj's spelling and gh's (`gh issue close -c`). `-F` reads a file, as for `comment`. No editor is opened: without either flag, `close` closes with no comment, as now. - If the comment fails, the issue is not closed. ## Done when `issue close <n> -c "..."` leaves the comment on the issue and the issue closed; the VM test checks it, and docs/agents/issue-tracker.md's **Close** line says to use it.
jeff closed this issue 2026-10-14 15:13:47 -05:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jeff/zfj#22
No description provided.