Add zfj run view #29

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

Part of #27

What

zfj run view <run number>.

  • Finds the run's ID through listActionRuns --run_number (ADR 0005); a number the repository does not have exits 1, saying no run <n> in <owner>/<repo>.
  • Shows the run — number, workflow, event, branch and commit, status, start and duration — and then its jobs from listActionRunJobs: name, status, attempt.
  • --json prints the run with its jobs inside it as a jobs array, as issue view --comments --json carries comments.
  • --web opens the run's page.
  • --exit-status exits 5 when the run ended in anything but success. Add 5 to the exit statuses in the usage text and README.

The lookup from run number to ID is shared by every later run command, so it belongs in one place.

Done when

zfj run view 43 shows v0.5.0's release run with its release and winget jobs, --exit-status exits 0 on it and 5 on a failed or cancelled run, and the README and usage describe it.

Part of #27 ## What `zfj run view <run number>`. - Finds the run's ID through `listActionRuns --run_number` (ADR 0005); a number the repository does not have exits 1, saying `no run <n> in <owner>/<repo>`. - Shows the run — number, workflow, event, branch and commit, status, start and duration — and then its jobs from `listActionRunJobs`: name, status, attempt. - `--json` prints the run with its jobs inside it as a `jobs` array, as `issue view --comments --json` carries `comments`. - `--web` opens the run's page. - `--exit-status` exits **5** when the run ended in anything but `success`. Add 5 to the exit statuses in the usage text and README. The lookup from run number to ID is shared by every later `run` command, so it belongs in one place. ## Done when `zfj run view 43` shows v0.5.0's release run with its `release` and `winget` jobs, `--exit-status` exits 0 on it and 5 on a failed or cancelled run, and the README and usage describe it.
jeff self-assigned this 2026-10-17 00:12:41 -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.

Reference
jeff/zfj#29
No description provided.