Share this article
Latest news
With KB5043178 to Release Preview Channel, Microsoft advises Windows 11 users to plug in when the battery is low
Copilot in Outlook will generate personalized themes for you to customize the app
Microsoft will raise the price of its 365 Suite to include AI capabilities
Death Stranding Director’s Cut is now Xbox X|S at a huge discount
Outlook will let users create custom account icons so they can tell their accounts apart easier
GitHub releases new “gh” command line tool in beta
2 min. read
Published onFebruary 13, 2020
published onFebruary 13, 2020
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
GitHub, whichMicrosoft acquired back in June 2018, has become one of the most popular ways for developers to collaborate on, share, and version control the software they’re working on, as well as using it to distribute code once it’s done. However, up until now, GitHub users had to use a graphical interface to get things done in GitHub, either to submit pull requests, or to track, view or create issues. Now however, with the help ofa new command line tool released in beta this week, developers have a new way of working with their code in GitHub.
The new command line tool (or “CLI,” command line interface), “gh” allows developers to stay in their work flow interacting with GitHub right from the terminal. This beta version starts with issues and pull requests, “because developers use them every day.” With the tool, devs can filter lists, view details, create issues or pull requests, and view status. It also allows users to easily check out pull requests:
One of the maintainers reviewed your pull request and requested changes. You probably switched branches since then, so useghto checkout the pull request branch. We never remember the right commands either!
Make the changes, push them, and soon enough the pull request is merged—congratulations!
You canlearn more about the GitHub CLI beta here.
Kip Kniskern
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Kip Kniskern