Downloads:

139,866

Downloads of v 2.13.0:

3,870

Last Update:

23 Jun 2022

Package Maintainer(s):

Software Author(s):

  • GitHub

Tags:

cli github git scm admin

GitHub CLI

  • 1
  • 2
  • 3

2.13.0 | Updated: 23 Jun 2022

Downloads:

139,866

Downloads of v 2.13.0:

3,870

Maintainer(s):

Software Author(s):

  • GitHub

  • 1
  • 2
  • 3
GitHub CLI 2.13.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install GitHub CLI, run the following command from the command line or from PowerShell:

>

To upgrade GitHub CLI, run the following command from the command line or from PowerShell:

>

To uninstall GitHub CLI, run the following command from the command line or from PowerShell:

>

Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade gh -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade gh -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install gh
  win_chocolatey:
    name: gh
    version: '2.13.0'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'gh' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.13.0'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller gh
{
    Name     = "gh"
    Version  = "2.13.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'gh':
  ensure   => '2.13.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 23 Jun 2022.

Description

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

NOTE: This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s) and let them know the package is no longer updating correctly.


tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$logMsi = Join-Path -Path $env:TEMP -ChildPath ("{0}-{1}-MsiInstall.log" -f $env:ChocolateyPackageName, $env:chocolateyPackageVersion)

$packageArgs = @{
    packageName    = $env:ChocolateyPackageName
    fileType       = 'MSI'
    silentArgs     = "/qn /norestart /l*v `"$logMsi`""
    file64         = Join-Path -Path $toolsDir -ChildPath "gh_$($env:ChocolateyPackageVersion)_windows_amd64.msi"
}

Install-ChocolateyInstallPackage @packageArgs
tools\gh_2.13.0_windows_amd64.msi
md5: 3D052A519B58ECA499B52089C315A9A3 | sha1: E84CF04007095D689BF56812756BF443952041C0 | sha256: 35DE663692A37A7A3EEDFA3B0497F3D666E1A0011AD36FCA65F5D6813ABBB335 | sha512: B6CCE9A68D2DFE4DA88153D81CBD73F0095C9BE7A72E5F06BAAEE9C98566A26E793AB6B163C8109B6D78B35348B73D4BAD6DFA4EF9904A4C197FB3D0C9A15363
tools\LICENSE.txt
From: https://raw.githubusercontent.com/cli/cli/master/LICENSE

LICENSE

MIT License

Copyright (c) 2019 GitHub Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

1. Please go to the project releases at https://github.com/cli/cli/releases;
2. Download the same binary file with the same version as included with the package;
3. From a PowerShell command line run:

     Get-FileHash <filename>

   against both the binary file included in the package and the one downloaded and they should match;

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
GitHub CLI 2.12.1 4010 Thursday, June 9, 2022 Approved
GitHub CLI 2.12.0 588 Wednesday, June 8, 2022 Approved
GitHub CLI 2.11.3 3562 Thursday, May 26, 2022 Approved
GitHub CLI 2.11.1 753 Tuesday, May 24, 2022 Approved
GitHub CLI 2.10.1 3873 Tuesday, May 10, 2022 Approved
GitHub CLI 2.9.0 4479 Tuesday, April 26, 2022 Approved
GitHub CLI 2.8.0 3482 Wednesday, April 13, 2022 Approved
GitHub CLI 2.7.0 3913 Wednesday, March 30, 2022 Approved
GitHub CLI 2.6.0 3631 Tuesday, March 15, 2022 Approved

This package has no dependencies.

Discussion for the GitHub CLI Package

Ground Rules:

  • This discussion is only about GitHub CLI and the GitHub CLI package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or GitHub CLI, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus