rtk-ai/rtk

`gh run view --job <id>` rejected with "Run ID required"

Open

#1568 opened on Apr 28, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
bugeffort-smallfilter-qualitygood first issue

Description

gh run view accepts --job <id> as an alternative to a positional run ID, but rtk rejects this form with rtk: Run ID required.

Reproduction:

$ gh run view --job 72893237475 --repo owner/repo --log
rtk: Run ID required

The same command works with RTK_DISABLED=1.

Per the gh CLI, the signature is gh run view [<run-id>] [flags] and --job is documented as a way to view a specific job — the positional run ID becomes optional in that case.

view_run requires a positional identifier and errors when none is found, even though --job and its value are correctly consumed into extra_args:

https://github.com/rtk-ai/rtk/blob/e1f2845df06a8d8b8325945dc4940ec5f530e4cc/src/cmds/git/gh_cmd.rs#L745-L749

--job is already listed in flags_with_value so its value is not mistaken for the run ID, but the --job-only invocation path was not handled:

https://github.com/rtk-ai/rtk/blob/e1f2845df06a8d8b8325945dc4940ec5f530e4cc/src/cmds/git/gh_cmd.rs#L124-L133

Environment: rtk 0.37.2, Windows 11, Git Bash.

Related: #416 / #477 fixed the case where --job's value was being eaten as the run ID, but did not cover the case where --job is the sole identifier.

Contributor guide

Tech stack
rust
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Rust knowledgeUnderstanding of CLI argument parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue involves the `view run` function in `src/cmds/git/gh cmd.rs`. The function currently requires a positional run ID, but when ` job` is provided, the run ID should be optional. The fix should check if ` job` is present and, if so, allow the absence of a positional argument. The relevant code sections are around lines 745-749 and 124-133. The maintainer may need to decide whether to extract the job ID from the ` job` flag or just skip the run ID requirement. The PR #416 and #477 provide context for previous related fixes.