Cancel and delete runs #33

Closed
opened 2026-10-16 23:59:33 -05:00 by jeff · 0 comments
Owner

Part of #27

What

zfj run cancel <run number> and zfj run delete <run number>, acting at once with no prompt, as issue close does.

  • cancel calls cancelActionRun. The operation answers 204 for a run already finished too, so say whether the run was still going: cancelled run 43 against run 43 had already finished.
  • delete calls deleteActionRun; Forgejo refuses a run that has not finished, and that refusal is exit 1 like any other.

Done when

Both work against a scratch run, the cases above print as described, and the README and usage describe them.

Part of #27 ## What `zfj run cancel <run number>` and `zfj run delete <run number>`, acting at once with no prompt, as `issue close` does. - `cancel` calls `cancelActionRun`. The operation answers 204 for a run already finished too, so say whether the run was still going: `cancelled run 43` against `run 43 had already finished`. - `delete` calls `deleteActionRun`; Forgejo refuses a run that has not finished, and that refusal is exit 1 like any other. ## Done when Both work against a scratch run, the cases above print as described, and the README and usage describe them.
jeff self-assigned this 2026-10-17 00:38:01 -05:00
jeff closed this issue 2026-10-17 10:34:18 -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.

Depends on
Reference
jeff/zfj#33
No description provided.