Skip to content

GitHub CLI 2.21.0

Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 22 Dec 22:17
7ffa87f

What's New

Selecting a default repository

When running a gh command for the first time in a local git repository that has multiple git remotes, gh used to interactively ask Which should be the base repository? so that the user may choose the git remote to default to when making queries to GitHub repositories. This had several problems:

  • Some users did not fully understand what they are being asked to choose;
  • The term “base repository” isn't an established GitHub term, except in the context of Pull Requests;
  • Once chosen, the only way to undo or change the choice made was to manually edit .git/config in the local repository.

The new behavior is as follows:

  • gh commands in a repository with multiple remotes will now error out until a default has been chosen.
  • The new gh repo set-default command can be used to select a default, view the selected value, or undo the selection altogether.

Thank you @bchadwic and @vilmibm! #4859 #6738

Internal git operations are now always authenticated

Previously, it could be confusing that a properly authenticated gh repo clone <repo> command could fail with a prompt for GitHub password. The underlying reason was that gh repo clone would shell out to git clone <url>, and from then on the authentication was entirely up to git's own credential management. If git wasn't set up to authenticate to GitHub, this could result in a generic password prompt, which appeared as if it was coming from gh.

The best general solution for setting up git to use credentials from GitHub CLI is to run gh auth setup-git. However, in this release, gh ensures that all underlying git operations are authenticated by gh, even if git on its own wasn't configured with a credential helper.

The way this works is by injecting extra configuration arguments when shelling out to git:

git -c credential.helper='!gh auth git-credential' clone <url>

Thank you @samcoe! #6541

The gh api command now accepts nested JSON parameters

The gh api command is similar to the popular curl tool, but with JSON encoding & parsing support and with built-in GitHub authentication. Sending JSON POST parameters was as easy as:

gh api <endpoint> -f 'param1=value1' -f 'param2=value2'

Now there is also a way to send nested JSON objects and arrays via a special brackets syntax when specifying field names:

gh api <endpoint> -f 'head[branch][name]=main'

gh api <endpoint> -f 'labels[]=bug' -f 'labels[]=priority-1'

Thank you @mislav! #6614

Other goodies

What's Changed

  • ap: avoid sending empty JSON body when no params for a non-GET request by @mislav in #6775
  • release: more resilient release creation and asset management by @mislav in #6667
    • A failed release create no longer leaves a temporary draft release behind
    • A draft release made by release create is now immediately referencable by tag name
    • Failed asset uploads will get retried several times
    • Fix clobbering existing files in release download by @mislav in #6694
  • pr create: exclude the current user from potential reviewers by @nsmag in #6464
  • codespace ports: use new domain in URLs of forwarded ports by @jshorty in #6705
  • Document installing GitHub CLI in Codespaces by @mislav in #6653
  • docs: Update installation instructions for WinGet by @vegerot in #6716
  • Update Cobra and make use of its new command grouping by @mislav in #6589
  • Update go-gh to v1.0.0 by @samcoe in #6618
  • Bump mislav/bump-homebrew-formula-action from 1 to 2 by @dependabot in #6634
  • Upgrade to Go 1.19 by @mislav in #6723
  • Use Prompter in pr package by @vilmibm in #6451
  • Use Prompter in release command by @vilmibm in #6711
  • Linter fixes by @samcoe in #6722
  • Bump goreleaser/goreleaser-action from 3 to 4 by @dependabot in #6727
  • Fix signing Windows exe on release by @mislav in #6776

New Contributors

Full Changelog: v2.20.2...v2.21.0