load test
By default, this was run on PowerShell on Windows, and even though the Actions environment is supposed to immediately exit on failures[1], this doesn't seem to have effect. Switching to bash for unified behavior on all platforms. [1]: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference |
||
|---|---|---|
| .github | ||
| .vscode | ||
| api | ||
| auth | ||
| cmd | ||
| command | ||
| context | ||
| git | ||
| internal/ghrepo | ||
| pkg | ||
| script | ||
| test | ||
| update | ||
| utils | ||
| .gitattributes | ||
| .gitignore | ||
| .goreleaser.yml | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| releasing.md | ||
| wix.json | ||
gh - The GitHub CLI tool
gh is GitHub on the command line. It brings pull requests, issues, and other GitHub concepts to
the terminal next to where you are already working with git and your code.
Usage
gh pr [status, list, view, checkout, create]gh issue [status, list, view, create]gh help
Check out the docs for more information.
Comparison with hub
For many years, hub was the unofficial GitHub CLI tool. gh is a new project for us to explore
what an official GitHub CLI tool can look like with a fundamentally different design. While both
tools bring GitHub to the terminal, hub behaves as a proxy to git and gh is a standalone
tool.
Installation
macOS
brew install github/gh/gh
Windows
MSI installers are available on the releases page.
Debian/Ubuntu Linux
- Download the
.debfile from the releases page sudo apt install git && sudo dpkg -i gh_*_linux_amd64.debinstall the downloaded file
Fedora/Centos Linux
- Download the
.rpmfile from the releases page sudo yum localinstall gh_*_linux_amd64.rpminstall the downloaded file
Other platforms
Install a prebuilt binary from the releases page or source compile by running make from the
project directory.
