# GitHub CLI 1.4.0

DevFeed: [GitHub CLI 1.4.0](<https://devfeed.tech/articles/github-cli-1-4-0-75319.md>)

Original publisher: [Read original article](<https://github.com/cli/cli/releases/tag/v1.4.0>)

Published: 2020-12-15T17:54:53Z

Content type: release

Language: en

Sources: [GitHub CLI](<https://devfeed.tech/sources/github-cli.md>)

Topics: [GitHub CLI extension](<https://devfeed.tech/topics/gh-extension.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [github-cli](<https://devfeed.tech/tags/github-cli.md>), [linux](<https://devfeed.tech/tags/linux.md>), [make](<https://devfeed.tech/tags/make.md>), [raspberry-pi](<https://devfeed.tech/tags/raspberry-pi.md>), [secret](<https://devfeed.tech/tags/secret.md>)

## AI overview

GitHub CLI 1.4.0 adds comment thread output for issue and pull request views, commands for managing repository and organization Actions secrets, and automatic Git credential setup during login. It also includes Linux binary and Raspberry Pi build updates.

## Source excerpt

## New features ### View issue and pull request comment threads (#2462, #2575) `gh issue view` and `gh pr view` commands now include the latest comment in their output. To render the entire comment thread, use the new `--comments` flag: ```sh $ gh issue view --comments ``` Note that, for now, `gh pr view` will only render regular comments and not review comments. ### Manage GitHub Actions secrets (#2529) The new `gh secret` commands enables setting, listing, and removing secrets for a repository or an organization. For example, to set a repository secret from file: ```sh $ gh secret set MY_SECRET < file.txt ``` To manage organization secrets, you will need to require an additional permission scope for GitHub CLI: ``` $ gh auth refresh --scopes admin:org ``` For more information, see [`gh help secret set`](https://cli.github.com/manual/gh_secret_set). ### Set up git credentials when logging into GitHub CLI (#2449) The `gh auth login` flow now includes a step to authenticate git as well when "HTTPS" is selected as the default clone protocol. This enables operations like `git clone`, `git push`, etc. to automatically work with GitHub on a pristine system after the user has authenticated to GitHub CLI. Previously, users had to authenticate git separately. This is enabled by the git credential helper. In the background, GitHub CLI runs this for the user: ```sh $ gh auth login #=> git credential approve <<<"url=https://USERNAME:TOKEN@github.com" ``` If no git credential helper was configured on the system, `gh` configures git to set itself as the credential helper for GitHub. If you had already logged in with GitHub CLI, you can sync your git credentials with those of GitHub CLI with: ```sh $ gh auth refresh --scopes workflow # (the additional "workflow" scope is required for pushing changes to any Actions workflow files) ``` ### Build system * Statically build our Linux binaries so they work on Alpine Linux #2556 * Add `armv6` build for Raspberry Pi #2621 * Add `make ins