Describe the feature or problem you’d like to solve
Related to #5493 and #3559 - when using the gh workflow and gh run subcommands, I'm usually trying to develop and debug a workflow. Being able to immediately watch the results of triggering a workflow, of rerunning a failed workflow run and the workflow run that results from a git push would all be incredibly useful.
Proposed solution
A flag for gh run watch that looks up the current running workflow run for a git ref would solve all three use cases. Alternatively, a utility command to look up the run id would be fine, since you could gh run watch $(gh run current-for <ref>) or something.
How will it benefit CLI and its users?
Having an end-to-end solution for "initiate a run, wait until done, review logs" that doesn't entail operator intervention two or three times has got to be a benefit.
Describe the feature or problem you’d like to solve
Related to #5493 and #3559 - when using the
gh workflowandgh runsubcommands, I'm usually trying to develop and debug a workflow. Being able to immediately watch the results of triggering a workflow, of rerunning a failed workflow run and the workflow run that results from agit pushwould all be incredibly useful.Proposed solution
A flag for
gh run watchthat looks up the current running workflow run for a git ref would solve all three use cases. Alternatively, a utility command to look up the run id would be fine, since you couldgh run watch $(gh run current-for <ref>)or something.How will it benefit CLI and its users?
Having an end-to-end solution for "initiate a run, wait until done, review logs" that doesn't entail operator intervention two or three times has got to be a benefit.