Describe the feature or problem you’d like to solve
When I watch a run and it fails, I typically want to go inspect the log, which currently requires me to switch the browser and click through the web interface. It would be great to have more information immediately or a simple way to get more information, especially when a run ends in error. Even viewing the log/run is quite difficult as I do not typically have the run ID to hand
Proposed solution
It may be useful to provide some or more of the following:
- a link to the run (as the output of
gh run view currently does)
- a link to the log
- make it easy to directly view the log through a command hint
- provide a menu-based option to view the log or open it in the browser
How will it benefit CLI and its users?
Faster way to understanding what went wrong without opening the browser and clicking or without figuring out another command and ID.
Describe the feature or problem you’d like to solve
When I watch a run and it fails, I typically want to go inspect the log, which currently requires me to switch the browser and click through the web interface. It would be great to have more information immediately or a simple way to get more information, especially when a run ends in error. Even viewing the log/run is quite difficult as I do not typically have the run ID to hand
Proposed solution
It may be useful to provide some or more of the following:
gh run viewcurrently does)How will it benefit CLI and its users?
Faster way to understanding what went wrong without opening the browser and clicking or without figuring out another command and ID.