Replies: 5 comments 7 replies
-
I could see this as a new "core" command, I think a new command would make more sense if the CLI made additional interactions with branches available to complement those available on the web today. While |
Beta Was this translation helpful? Give feedback.
-
Something like Git Graph in VS Code ? What I'm really missing, is an easy way to collect and visualise Github commit statuses. |
Beta Was this translation helpful? Give feedback.
-
I like the idea of a command namespace existing around commit information; especially for answering questions like "which PR introduced this SHA?" "what SHAs did this PR introduce?" "what did CI look like on this SHA?" I'm concerned that |
Beta Was this translation helpful? Give feedback.
-
Just wanted to throw this out there because I was looking for the same thing. The I solved this last point with the following command: gh api \
-H "Accept: application/vnd.github+json" \
/repos/{YOUR_ORG}/{YOUR_REPO}/commits/{YOUR_COMMIT}/status It doesn't necessarily retrieve in a consolidated, dashboard view like the GitHub API Reference - note there is an additional section specifically for API calls with the GitHub CLI. |
Beta Was this translation helpful? Give feedback.
-
Following the PAGER= gh api repos/myorg/myrepo/commits -f sha=mybranch --method GET --jq '.[] | select(.committer != null) | .commit.message' |
Beta Was this translation helpful? Give feedback.
-
It'd be really useful if the CLI had a command to show commit history for a given branch, similar to the GitHub "commits view" (
<repo>/commits/<branch>
URL), as an alternative to browsing the GitHub UI for this information.The commit history alone is probably not helpful (duplicative of
git log
output), but a combination of the following data could be really helpful.This GitHub documentation page links to this commits view page as an example, which could be used for inspiration.
Beta Was this translation helpful? Give feedback.
All reactions