Describe the feature or problem you’d like to solve
Often, when debugging a CI issue, there's a tight(-ish) loop of git commit -am "fix: CI"; git push; gh workflow run, then followed by some variation of gh run watch - which either requires choosing from a TUI list or (now) copypasta of the run ID from the gh workflow run.
It would be ideal to be able to either have a wicked gnarly one-liner to arrow-up to, or be able to script the "commit-run-watch-notify-log" loop. #12695 gets us so close...
Proposed solution
gh workflow run --watch would be a great first step.
gh workflow run --output=json would also be great, since it would make using a tool like jq to pull the run ID out much easier
Additional context
> gh workflow run --output=json
{
"status": "created",
"run_id": 123412341234
"probably": "other info"
}
Describe the feature or problem you’d like to solve
Often, when debugging a CI issue, there's a tight(-ish) loop of
git commit -am "fix: CI"; git push; gh workflow run, then followed by some variation ofgh run watch- which either requires choosing from a TUI list or (now) copypasta of the run ID from thegh workflow run.It would be ideal to be able to either have a wicked gnarly one-liner to arrow-up to, or be able to script the "commit-run-watch-notify-log" loop. #12695 gets us so close...
Proposed solution
gh workflow run --watchwould be a great first step.gh workflow run --output=jsonwould also be great, since it would make using a tool likejqto pull the run ID out much easierAdditional context