load test
Find a file
chemotaxis a291b3eed3
Fix grammar in repo create prompt (#5557)
* Use plural linking verb

While it looks like you could use "there's" informally, grammatically, it should be "are" since "commits" is plural.

<https://dictionary.cambridge.org/us/grammar/british-grammar/there-is-there-s-and-there-are>

* Omit "the"

I created a remote called "github" and got this prompt:

> Would you like to push commits from the current branch to the "github"?

Normally, the default name "origin" doesn't sound bad in that prompt,
but using the name "github" made the prompt sound like something wasn't
right to my American English-speaking ears.

Here are a few options.  Yes, I know English grammar sucks, to put it
mildly.  But, hopefully, the following options and explanations make
sense.

Get rid of "the".  This is the option I went with.  "github" acts as a
proper noun, so no determiner is needed.  If you substitute your own
name for "github" in the original prompt above, you get the same effect:

> Would you like to push commits from the current branch to "github"?

Add the implicit word "remote".  "github" now acts as an adjective and
"the" refers to "remote":

> Would you like to push commits from the current branch to the "github" remote?

Or, combine the two.  This last option relies on the fact that
instructions and manuals often omit definite articles because most
articles are definite.  See the [zero-marking][2] article on Wikipedia.
The original prompt already does this by omitting "the" before the word
"commits":

> Would you like to push commits from the current branch to "github" remote?

Reference:

[1]: http://writing.umn.edu/sws/quickhelp/grammar/articlesproper.html

[2]: https://en.wikipedia.org/wiki/Zero-marking_in_English
2022-05-02 10:21:59 +02:00
.devcontainer Adds internal codespace developer flags (#5287) 2022-03-09 15:59:29 +00:00
.github Bump github/codeql-action from 1 to 2 2022-04-25 14:24:46 +00:00
.vscode Add VS Code settings 2019-10-07 16:36:23 +02:00
api Remove Stringer from ghrepo.Interface (#5536) 2022-04-28 08:58:34 +02:00
build/windows Resolve PR feedback 2021-09-18 09:23:43 -07:00
cmd Add autocomplete descriptions for aliases and extensions (#5447) 2022-04-26 13:08:16 +02:00
context Rename the module to "github.com/cli/cli/v2" 2021-08-25 12:41:30 +02:00
docs [install_linux.md]: fix typo (#5446) 2022-04-13 07:24:27 +02:00
git pr merge switch to base branch if available (#5251) 2022-03-14 14:02:57 +02:00
internal Remove Stringer from ghrepo.Interface (#5536) 2022-04-28 08:58:34 +02:00
pkg Fix grammar in repo create prompt (#5557) 2022-05-02 10:21:59 +02:00
script Replace ioutil with io and os (#5498) 2022-04-26 13:07:44 +02:00
test Pass web browser to each individual command 2021-03-19 21:22:37 +01:00
utils Merge pull request #5076 from cli/multi-devcontainer 2022-04-20 12:06:23 -07:00
.gitattributes Retire copy-release-to-another-repo action 2020-01-29 16:13:07 +01:00
.gitignore Port select portions of Makefile to script/build.go 2021-01-08 22:35:57 +01:00
.golangci.yml Prevent further use of SetPrepareCmd and InitCmdStubber 2021-01-18 22:44:53 +01:00
.goreleaser.yml Rotate our Windows signing certificates (#5196) 2022-02-15 17:23:39 +01:00
CODEOWNERS Fix CODEOWNERS for codespaces 2021-11-15 20:05:54 +01:00
go.mod Bump github.com/google/go-cmp from 0.5.7 to 0.5.8 (#5533) 2022-04-27 21:40:26 +02:00
go.sum Bump github.com/google/go-cmp from 0.5.7 to 0.5.8 (#5533) 2022-04-27 21:40:26 +02:00
LICENSE Create LICENSE 2019-11-21 13:22:23 -06:00
Makefile Tweak build scripts to enable cross-compiling 2021-04-09 15:48:12 +02:00
README.md Update winget installation instructions 2021-10-13 15:01:50 +01:00

GitHub CLI

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.

screenshot of gh pr status

GitHub CLI is available for repositories hosted on GitHub.com and GitHub Enterprise Server 2.20+, and to install on macOS, Windows, and Linux.

Documentation

See the manual for setup and usage instructions.

Contributing

If anything feels off, or if you feel that some functionality is missing, please check out the contributing page. There you will find instructions for sharing your feedback, building the tool locally, and submitting pull requests to the project.

Installation

macOS

gh is available via Homebrew, MacPorts, Conda, Spack, and as a downloadable binary from the releases page.

Homebrew

Install: Upgrade:
brew install gh brew upgrade gh

MacPorts

Install: Upgrade:
sudo port install gh sudo port selfupdate && sudo port upgrade gh

Conda

Install: Upgrade:
conda install gh --channel conda-forge conda update gh --channel conda-forge

Additional Conda installation options available on the gh-feedstock page.

Spack

Install: Upgrade:
spack install gh spack uninstall gh && spack install gh

Linux & BSD

gh is available via Homebrew, Conda, Spack, and as downloadable binaries from the releases page.

For instructions on specific distributions and package managers, see Linux & BSD installation.

Windows

gh is available via WinGet, scoop, Chocolatey, Conda, and as downloadable MSI.

WinGet

Install: Upgrade:
winget install --id GitHub.cli winget upgrade --id GitHub.cli

scoop

Install: Upgrade:
scoop install gh scoop update gh

Chocolatey

Install: Upgrade:
choco install gh choco upgrade gh

Signed MSI

MSI installers are available for download on the releases page.

GitHub Actions

GitHub CLI comes pre-installed in all GitHub-Hosted Runners.

Other platforms

Download packaged binaries from the releases page.

Build from source

See here on how to build GitHub CLI from source.

Comparison with hub

For many years, hub was the unofficial GitHub CLI tool. gh is a new project that helps us 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. Check out our more detailed explanation to learn more.