GitHub CLI 1.0 (github.blog)

Article summary

GitHub CLI 1.0 is now available, allowing users to interact with GitHub from their terminal. It enables users to run their entire GitHub workflow from the terminal, from issues through releases, and to script nearly any action. The CLI has been in beta since earlier this year and has seen significant usage, with over 250,000 pull requests and 350,000 merges created using the tool. The GitHub CLI is available to download on Windows, macOS, and Linux.

Main themes

• GitHub CLI
• Git commands
• Automation and scripting
• Graphical interfaces
• Development workflows
• Vendor lock-in
• API interaction
• Command-line interfaces
• User productivity

What commenters say

• The GitHub CLI is seen as a complement to traditional git commands, not a replacement, and is useful for interacting with GitHub-specific features like issues and pull requests.
• Some users are concerned that the CLI may lead to 'unlearning' of traditional git commands, especially for those not using GitHub.
• The CLI is viewed as a way to tightly couple development workflows to GitHub, potentially making it more difficult to switch to other vendors in the future.
• Others see the CLI as a useful tool for automation and scripting, and appreciate its ability to interact with the GitHub API.
• There is disagreement about the usefulness of a CLI for managing GitHub workflows, with some preferring graphical interfaces and others finding the CLI more efficient.
• The CLI is seen as a way to improve focus and reduce context switching, as well as to enable automation and scripting of GitHub workflows.
• Some users appreciate the CLI's ability to provide a concise and clean format for viewing information, such as open issues and pull requests.