Downloads:
365,308
Downloads of v 2.21.0:
405
Last Update:
23 Dec 2022
Package Maintainer(s):
Software Author(s):
- GitHub
Tags:
cli github git scm admin- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
GitHub CLI
This is not the latest version of GitHub CLI available.
- 1
- 2
- 3
2.21.0 | Updated: 23 Dec 2022
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
365,308
Downloads of v 2.21.0:
405
Maintainer(s):
Software Author(s):
- GitHub
GitHub CLI 2.21.0
This is not the latest version of GitHub CLI available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
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:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download gh --internalize --version=2.21.0 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade gh -y --source="'INTERNAL REPO URL'" --version="'2.21.0'" [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'" --version="'2.21.0'"
$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.21.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.21.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller gh
{
Name = "gh"
Version = "2.21.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'gh':
ensure => '2.21.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 Dec 2022.
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.
md5: DA9464935F8D35C223D654F8FC5009A4 | sha1: F21B4BD3D7A80B8865BF2CFB6611C8B185E9443A | sha256: DFB156E2FCBDD02DB021E52D457BFF9196AF83E0A0EE8800AB1388B49C395DEF | sha512: 4FCEAB8107211DD50A104ACAD9D5E1F5F2AADD201602A93FFD34887BF5A9164013805129974B68827B0BD9CCE5F49A5D405CC21B749155D9FB9F952AD1648760
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.
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community in verifying that this package's contents are trustworthy.
To verify the files using the project source:
1. Please go to the project source location and download the release matching the package version.
2. Use Get-FileHash -Path <FILE TO VERIFY> to get the file hash value from both the official release file (from step 1 above) and the file from the package and compare them.
x64 URL: https://github.com/cli/cli/releases/download/v2.21.0/gh_2.21.0_windows_amd64.msi
x64 Checksum Type: SHA256
x64 Checksum: DFB156E2FCBDD02DB021E52D457BFF9196AF83E0A0EE8800AB1388B49C395DEF
Log in or click on link to see number of positives.
- gh.2.21.0.nupkg (9691f535968b) - ## / 64
- gh_2.21.0_windows_amd64.msi (dfb156e2fcbd) - ## / 61
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.48.0 | 3683 | Wednesday, April 17, 2024 | Approved | |
GitHub CLI 2.47.0 | 4928 | Wednesday, April 3, 2024 | Approved | |
GitHub CLI 2.46.0 | 4776 | Thursday, March 21, 2024 | Approved | |
GitHub CLI 2.45.0 | 5492 | Tuesday, March 5, 2024 | Approved | |
GitHub CLI 2.44.1 | 4858 | Friday, February 16, 2024 | Approved | |
GitHub CLI 2.44.0 | 793 | Thursday, February 15, 2024 | Approved | |
GitHub CLI 2.43.1 | 4774 | Thursday, February 1, 2024 | Approved | |
GitHub CLI 2.43.0 | 492 | Wednesday, January 31, 2024 | Approved | |
GitHub CLI 2.42.1 | 5267 | Wednesday, January 17, 2024 | Approved | |
GitHub CLI 2.42.0 | 2407 | Thursday, January 11, 2024 | Approved | |
GitHub CLI 2.41.0 | 1741 | Monday, January 8, 2024 | Approved | |
GitHub CLI 2.40.1 | 6894 | Wednesday, December 13, 2023 | Approved | |
GitHub CLI 2.40.0 | 2551 | Thursday, December 7, 2023 | Approved | |
GitHub CLI 2.39.2 | 3331 | Monday, November 27, 2023 | Approved | |
GitHub CLI 2.39.1 | 4726 | Tuesday, November 14, 2023 | Approved | |
GitHub CLI 2.39.0 | 36 | Tuesday, November 14, 2023 | Approved | |
GitHub CLI 2.38.0 | 3992 | Wednesday, November 1, 2023 | Approved | |
GitHub CLI 2.37.0 | 4727 | Tuesday, October 17, 2023 | Approved | |
GitHub CLI 2.36.0 | 6197 | Tuesday, October 3, 2023 | Approved | |
GitHub CLI 2.35.0 | 6018 | Tuesday, September 19, 2023 | Approved | |
GitHub CLI 2.34.0 | 4517 | Wednesday, September 6, 2023 | Approved | |
GitHub CLI 2.33.0 | 4394 | Monday, August 21, 2023 | Approved | |
GitHub CLI 2.32.1 | 10459 | Tuesday, July 25, 2023 | Approved | |
GitHub CLI 2.32.0 | 6094 | Wednesday, July 12, 2023 | Approved | |
GitHub CLI 2.31.0 | 5105 | Wednesday, June 21, 2023 | Approved | |
GitHub CLI 2.30.0 | 5679 | Tuesday, May 30, 2023 | Approved | |
GitHub CLI 2.29.0 | 5767 | Wednesday, May 10, 2023 | Approved | |
GitHub CLI 2.28.0 | 5062 | Tuesday, April 25, 2023 | Approved | |
GitHub CLI 2.27.0 | 5173 | Saturday, April 8, 2023 | Approved | |
GitHub CLI 2.26.1 | 1615 | Wednesday, April 5, 2023 | Approved | |
GitHub CLI 2.25.1 | 5440 | Tuesday, March 21, 2023 | Approved | |
GitHub CLI 2.25.0 | 728 | Tuesday, March 21, 2023 | Approved | |
GitHub CLI 2.24.3 | 4046 | Thursday, March 9, 2023 | Approved | |
GitHub CLI 2.24.0 | 823 | Wednesday, March 8, 2023 | Approved | |
GitHub CLI 2.23.0 | 7582 | Wednesday, February 8, 2023 | Approved | |
GitHub CLI 2.22.1 | 5214 | Friday, January 27, 2023 | Approved | |
GitHub CLI 2.22.0 | 1541 | Wednesday, January 25, 2023 | Approved | |
GitHub CLI 2.21.2 | 7295 | Wednesday, January 4, 2023 | Approved | |
GitHub CLI 2.21.1 | 2599 | Friday, December 23, 2022 | Approved | |
GitHub CLI 2.21.0 | 405 | Friday, December 23, 2022 | Approved | |
GitHub CLI 2.20.2 | 10847 | Tuesday, November 15, 2022 | Approved | |
GitHub CLI 2.20.0 | 1043 | Sunday, November 13, 2022 | Approved | |
GitHub CLI 2.19.0 | 4628 | Thursday, November 3, 2022 | Approved | |
GitHub CLI 2.18.1 | 4154 | Friday, October 21, 2022 | Approved | |
GitHub CLI 2.18.0 | 974 | Tuesday, October 18, 2022 | Approved | |
GitHub CLI 2.17.0 | 4400 | Wednesday, October 5, 2022 | Approved | |
GitHub CLI 2.16.1 | 2040 | Friday, September 30, 2022 | Approved | |
GitHub CLI 2.15.0 | 6143 | Tuesday, September 6, 2022 | Approved | |
GitHub CLI 2.14.7 | 3914 | Thursday, August 25, 2022 | Approved | |
GitHub CLI 2.14.6 | 625 | Wednesday, August 24, 2022 | Approved | |
GitHub CLI 2.14.5 | 285 | Wednesday, August 24, 2022 | Approved | |
GitHub CLI 2.14.4 | 3628 | Wednesday, August 10, 2022 | Approved | |
GitHub CLI 2.14.3 | 3808 | Tuesday, July 26, 2022 | Approved | |
GitHub CLI 2.14.2 | 3170 | Thursday, July 14, 2022 | Approved | |
GitHub CLI 2.14.1 | 1217 | Tuesday, July 12, 2022 | Approved | |
GitHub CLI 2.14.0 | 345 | Tuesday, July 12, 2022 | Approved | |
GitHub CLI 2.13.0 | 5552 | Thursday, June 23, 2022 | Approved | |
GitHub CLI 2.12.1 | 4065 | Thursday, June 9, 2022 | Approved | |
GitHub CLI 2.12.0 | 634 | Wednesday, June 8, 2022 | Approved | |
GitHub CLI 2.11.3 | 3651 | Thursday, May 26, 2022 | Approved | |
GitHub CLI 2.11.1 | 947 | Tuesday, May 24, 2022 | Approved | |
GitHub CLI 2.10.1 | 4043 | Tuesday, May 10, 2022 | Approved | |
GitHub CLI 2.9.0 | 5232 | Tuesday, April 26, 2022 | Approved | |
GitHub CLI 2.8.0 | 3642 | Wednesday, April 13, 2022 | Approved | |
GitHub CLI 2.7.0 | 3985 | Wednesday, March 30, 2022 | Approved | |
GitHub CLI 2.6.0 | 3819 | Tuesday, March 15, 2022 | Approved | |
GitHub CLI 2.5.2 | 4526 | Tuesday, March 1, 2022 | Approved | |
GitHub CLI 2.5.1 | 3734 | Tuesday, February 15, 2022 | Approved | |
GitHub CLI 2.5.0 | 3885 | Tuesday, February 1, 2022 | Approved | |
GitHub CLI 2.4.0 | 8333 | Tuesday, December 21, 2021 | Approved | |
GitHub CLI 2.3.0 | 4267 | Thursday, December 2, 2021 | Approved | |
GitHub CLI 2.2.0 | 7325 | Tuesday, October 26, 2021 | Approved | |
GitHub CLI 2.1.0 | 2637 | Friday, October 15, 2021 | Approved | |
GitHub CLI 2.0.0 | 8996 | Tuesday, August 24, 2021 | Approved | |
GitHub CLI 1.14.0 | 3194 | Thursday, August 5, 2021 | Approved | |
GitHub CLI 1.13.1 | 2686 | Wednesday, July 21, 2021 | Approved | |
GitHub CLI 1.12.1 | 3185 | Thursday, July 1, 2021 | Approved | |
GitHub CLI 1.12.0 | 530 | Wednesday, June 30, 2021 | Approved | |
GitHub CLI 1.11.0 | 3949 | Friday, June 4, 2021 | Approved | |
GitHub CLI 1.10.3 | 2450 | Friday, May 21, 2021 | Approved | |
GitHub CLI 1.10.2 | 776 | Wednesday, May 19, 2021 | Approved | |
GitHub CLI 1.10.1 | 118 | Wednesday, May 19, 2021 | Approved | |
GitHub CLI 1.10.0 | 501 | Tuesday, May 18, 2021 | Approved | |
GitHub CLI 1.9.2 | 4169 | Wednesday, April 21, 2021 | Approved | |
GitHub CLI 1.9.1 | 1474 | Thursday, April 15, 2021 | Approved | |
GitHub CLI 1.9.0 | 503 | Thursday, April 15, 2021 | Approved | |
GitHub CLI 1.8.1 | 2005 | Friday, April 2, 2021 | Approved | |
GitHub CLI 1.8.0 | 498 | Wednesday, March 31, 2021 | Approved | |
GitHub CLI 1.7.0 | 4034 | Friday, March 5, 2021 | Approved | |
GitHub CLI 1.6.2 | 1858 | Tuesday, February 23, 2021 | Approved | |
GitHub CLI 1.6.1 | 1086 | Friday, February 19, 2021 | Approved | |
GitHub CLI 1.6.0 | 465 | Thursday, February 18, 2021 | Approved | |
GitHub CLI 1.5.0 | 3599 | Friday, January 22, 2021 | Approved | |
GitHub CLI 1.4.0 | 4391 | Tuesday, December 15, 2020 | Approved | |
GitHub CLI 1.3.1 | 2015 | Thursday, December 3, 2020 | Approved | |
GitHub CLI 1.3.0 | 1502 | Wednesday, November 25, 2020 | Approved | |
GitHub CLI 1.2.1 | 2057 | Wednesday, November 11, 2020 | Approved | |
GitHub CLI 1.2.0 | 2497 | Tuesday, October 27, 2020 | Approved | |
GitHub CLI 1.1.0 | 3311 | Tuesday, October 6, 2020 | Approved | |
GitHub CLI 1.0.0 | 4436 | Wednesday, September 16, 2020 | Approved | |
GitHub CLI 0.12.0 | 738 | Tuesday, September 8, 2020 | Approved | |
GitHub CLI 0.11.1 | 2082 | Wednesday, July 29, 2020 | Approved | |
GitHub CLI 0.11.0 | 818 | Friday, July 17, 2020 | Approved | |
GitHub CLI 0.10.1 | 1254 | Wednesday, June 24, 2020 | Approved | |
GitHub CLI 0.10.0 | 830 | Friday, June 12, 2020 | Approved | |
GitHub CLI 0.9.0 | 1067 | Tuesday, May 26, 2020 | Approved | |
GitHub CLI 0.8.0 | 834 | Tuesday, May 12, 2020 | Approved | |
GitHub CLI 0.7.0 | 724 | Thursday, April 23, 2020 | Approved | |
GitHub CLI 0.6.4 | 456 | Monday, April 6, 2020 | Approved | |
GitHub CLI 0.6.2 | 146 | Thursday, March 26, 2020 | Approved | |
GitHub CLI 0.6.1 | 551 | Monday, March 9, 2020 | Approved | |
GitHub CLI 0.5.5 | 804 | Friday, February 14, 2020 | Approved |
Copyright 2020 GitHub
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! https://github.com/cli/cli/pull/4859 https://github.com/cli/cli/pull/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! https://github.com/cli/cli/pull/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! https://github.com/cli/cli/pull/6614
Other goodies
- Add
issue lock/unlock
andpr lock/unlock
commands by @chemotaxis in https://github.com/cli/cli/pull/5333 release create
: add--verify-tag
flag by @luanzeba in https://github.com/cli/cli/pull/6632release create
: add--exclude-pre-releases
flag by @owenvoke in https://github.com/cli/cli/pull/6625repo create
: prompt for repository owner in interactive mode by @twelvelabs in https://github.com/cli/cli/pull/6578repo edit
: add--allow-update-branch
flag by @browniebroke in https://github.com/cli/cli/pull/6706extension upgrade
: show version change information by @despreston in https://github.com/cli/cli/pull/6647- Codespaces: Use
-R
for--repo
shorthand and deprecate-r
by @cmbrose in https://github.com/cli/cli/pull/6725 codespace create
: allow setting display name for the new codespace by @despreston in https://github.com/cli/cli/pull/6739alias list
: change output format to YAML by @ptforness in https://github.com/cli/cli/pull/6603- JSON export improvements:
- Add
author
information inpr list
JSON output by @hirasawayuki in https://github.com/cli/cli/pull/5049 - Add
isDraft
tosearch prs
json options, matchingpr view
by @mgabeler-lee-6rs in https://github.com/cli/cli/pull/6704 - Expose commit SHA in PR reviews JSON export by @mislav in https://github.com/cli/cli/pull/6646
- Add
What's Changed
ap
: avoid sending empty JSON body when no params for a non-GET request by @mislav in https://github.com/cli/cli/pull/6775release
: more resilient release creation and asset management by @mislav in https://github.com/cli/cli/pull/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 https://github.com/cli/cli/pull/6694
- A failed
pr create
: exclude the current user from potential reviewers by @nsmag in https://github.com/cli/cli/pull/6464codespace ports
: use new domain in URLs of forwarded ports by @jshorty in https://github.com/cli/cli/pull/6705- Document installing GitHub CLI in Codespaces by @mislav in https://github.com/cli/cli/pull/6653
- docs: Update installation instructions for WinGet by @vegerot in https://github.com/cli/cli/pull/6716
- Update Cobra and make use of its new command grouping by @mislav in https://github.com/cli/cli/pull/6589
- Update go-gh to v1.0.0 by @samcoe in https://github.com/cli/cli/pull/6618
- Bump mislav/bump-homebrew-formula-action from 1 to 2 by @dependabot in https://github.com/cli/cli/pull/6634
- Upgrade to Go 1.19 by @mislav in https://github.com/cli/cli/pull/6723
- Use Prompter in
pr
package by @vilmibm in https://github.com/cli/cli/pull/6451 - Use Prompter in
release
command by @vilmibm in https://github.com/cli/cli/pull/6711 - Linter fixes by @samcoe in https://github.com/cli/cli/pull/6722
- Bump goreleaser/goreleaser-action from 3 to 4 by @dependabot in https://github.com/cli/cli/pull/6727
- Fix signing Windows exe on release by @mislav in https://github.com/cli/cli/pull/6776
New Contributors
- @luanzeba made their first contribution in https://github.com/cli/cli/pull/6632
- @twelvelabs made their first contribution in https://github.com/cli/cli/pull/6578
- @vegerot made their first contribution in https://github.com/cli/cli/pull/6716
- @ptforness made their first contribution in https://github.com/cli/cli/pull/6603
Full Changelog: https://github.com/cli/cli/compare/v2.20.2...v2.21.0
This package has no dependencies.
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.