{"id":79424,"date":"2026-10-20T04:40:43","date_gmt":"2026-10-20T04:40:43","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=79424"},"modified":"2026-10-20T04:40:47","modified_gmt":"2026-10-20T04:40:47","slug":"how-to-install-github-cli-gh-on-macos-windows-and-linux-complete-step-by-step-guide","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/how-to-install-github-cli-gh-on-macos-windows-and-linux-complete-step-by-step-guide\/","title":{"rendered":"How to Install GitHub CLI (gh) on macOS, Windows, and Linux: Complete Step-by-Step Guide"},"content":{"rendered":"\n

SEO Title:<\/strong> How to Install GitHub CLI (gh) on Mac, Windows & Linux \u2013 2026 Guide<\/p>\n\n\n\n

Meta Description:<\/strong> Learn how to install GitHub CLI (gh) on macOS, Windows 10\/11, Ubuntu, Debian, Fedora, RHEL, and CentOS. Includes commands, authentication, Git integration, updates, and troubleshooting.<\/p>\n\n\n\n

Focus Keywords:<\/strong> GitHub CLI installation, install gh CLI, GitHub CLI Mac, GitHub CLI Windows, GitHub CLI Ubuntu, install gh Linux, GitHub CLI commands, gh auth login, GitHub CLI Homebrew<\/p>\n\n\n\n

\n\n\n\n

1. Introduction<\/h2>\n\n\n\n

GitHub is one of the most widely used platforms for hosting source code, managing pull requests, tracking issues, and automating software development workflows.<\/p>\n\n\n\n

While most developers interact with GitHub through a web browser, GitHub also provides an official command-line tool called GitHub CLI (<\/strong>gh<\/strong><\/code>)<\/strong>.<\/p>\n\n\n\n

GitHub CLI brings GitHub functionality directly into your terminal, allowing you to manage repositories, pull requests, issues, releases, and workflows without repeatedly switching to a browser.<\/p>\n\n\n\n

Whether you are a developer, DevOps engineer, system administrator, platform engineer, or automation specialist, learning GitHub CLI can significantly simplify everyday development tasks.<\/p>\n\n\n\n

In this comprehensive tutorial, you will learn how to:<\/p>\n\n\n\n

    \n
  • Install GitHub CLI on macOS, including Intel and Apple Silicon Macs.<\/li>\n\n\n\n
  • Install GitHub CLI on Windows 10 and Windows 11.<\/li>\n\n\n\n
  • Install GitHub CLI on Ubuntu and Debian.<\/li>\n\n\n\n
  • Install GitHub CLI on Fedora, RHEL, and CentOS.<\/li>\n\n\n\n
  • Install GitHub CLI on Amazon Linux and other Linux distributions.<\/li>\n\n\n\n
  • Verify that the installation was successful.<\/li>\n\n\n\n
  • Authenticate GitHub CLI with your GitHub account.<\/li>\n\n\n\n
  • Configure Git to use GitHub CLI authentication.<\/li>\n\n\n\n
  • Execute essential GitHub CLI commands.<\/li>\n\n\n\n
  • Upgrade, troubleshoot, and uninstall GitHub CLI.<\/li>\n<\/ul>\n\n\n\n

    Let’s begin.<\/p>\n\n\n\n

    2. What Is GitHub CLI?<\/h2>\n\n\n\n

    GitHub CLI is GitHub’s official open-source command-line tool.<\/p>\n\n\n\n

    Its executable is named:<\/p>\n\n\n

    gh<\/code><\/span><\/pre>\n\n\n
    It allows users to manage GitHub resources from a terminal using simple commands.<\/p>\n\n\n\n
    For example, instead of visiting GitHub in your browser to review pull requests, you can execute:<\/p>\n\n\n
    gh pr list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    To list repository issues:<\/p>\n\n\n
    gh issue list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    To clone a GitHub repository:<\/p>\n\n\n
    gh repo clone<\/span> OWNER\/REPOSITORY<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    To check your authentication status:<\/p>\n\n\n
    gh auth status<\/code><\/span><\/pre>\n\n\n
    Key Features of GitHub CLI<\/h3>\n\n\n\n
      \n
    • Authenticate with GitHub.com and supported GitHub Enterprise installations.<\/li>\n\n\n\n
    • Create, view, review, and merge pull requests.<\/li>\n\n\n\n
    • Create and manage GitHub issues.<\/li>\n\n\n\n
    • Clone, fork, and manage repositories.<\/li>\n\n\n\n
    • View GitHub Actions workflows and workflow runs.<\/li>\n\n\n\n
    • Manage GitHub releases.<\/li>\n\n\n\n
    • Access the GitHub REST and GraphQL APIs.<\/li>\n\n\n\n
    • Integrate GitHub operations into scripts and automation.<\/li>\n\n\n\n
    • Work with GitHub from macOS, Windows, and Linux terminals.<\/li>\n<\/ul>\n\n\n\n
      Git vs. GitHub CLI: What Is the Difference?<\/h3>\n\n\n\n
      Git and GitHub CLI serve different purposes.<\/p>\n\n\n\n
      Feature<\/th>Git<\/th>GitHub CLI (gh<\/code>)<\/th><\/tr>
      Primary purpose<\/td>Version control<\/td>GitHub platform management<\/td><\/tr>
      Command<\/td>git<\/code><\/td>gh<\/code><\/td><\/tr>
      Commit code<\/td>Yes<\/td>Uses Git for normal version-control operations<\/td><\/tr>
      Manage pull requests<\/td>Not directly<\/td>Yes<\/td><\/tr>
      Manage GitHub issues<\/td>No<\/td>Yes<\/td><\/tr>
      Clone repositories<\/td>Yes<\/td>Yes, through Git<\/td><\/tr>
      Manage GitHub Actions<\/td>No<\/td>Yes<\/td><\/tr>
      Manage GitHub releases<\/td>No<\/td>Yes<\/td><\/tr>
      Access GitHub API<\/td>Not directly<\/td>Yes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      Important:<\/strong> GitHub CLI does not replace Git. It complements Git by providing commands for GitHub-specific workflows.<\/p>\n\n\n\n
      For normal repository operations, install both Git and GitHub CLI.<\/p>\n\n\n\n
      \n\n\n\n
      3. Prerequisites<\/h2>\n\n\n\n
      Before installing GitHub CLI, make sure your computer meets the following requirements.<\/p>\n\n\n\n
      Requirement<\/th>Description<\/th><\/tr>
      Operating system<\/td>Supported macOS, Windows, or Linux<\/td><\/tr>
      CPU architecture<\/td>Compatible architecture such as x86-64 or ARM64<\/td><\/tr>
      Internet connection<\/td>Required to download packages and connect to GitHub<\/td><\/tr>
      Terminal<\/td>Terminal, Bash, Zsh, PowerShell, or Command Prompt<\/td><\/tr>
      Package manager<\/td>Homebrew, WinGet, APT, DNF, or another supported installer<\/td><\/tr>
      GitHub account<\/td>Required for authenticated GitHub operations<\/td><\/tr>
      Git<\/td>Recommended for repository operations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      You can create a free GitHub account at:<\/p>\n\n\n\n
      \nhttps:\/\/github.com\/signup\n<\/div><\/figure>\n\n\n\n
      Check Whether Git Is Installed<\/h3>\n\n\n\n
      On macOS or Linux:<\/p>\n\n\n
      git --version<\/code><\/span><\/pre>\n\n\n
      On Windows PowerShell:<\/p>\n\n\n
      git --version<\/code><\/span><\/pre>\n\n\n
      If Git is installed, you will see its version.<\/p>\n\n\n\n
      Example:<\/p>\n\n\n
      git<\/span> version<\/span> 2.x<\/span>.x<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      If Git is not installed, visit:<\/p>\n\n\n\n
      \nhttps:\/\/git-scm.com\/downloads\n<\/div><\/figure>\n\n\n\n
      You can install GitHub CLI independently, but Git should also be installed if you intend to clone repositories, commit changes, or push code.<\/p>\n\n\n\n
      \n\n\n\n
      4. How to Install GitHub CLI on macOS<\/h1>\n\n\n\n
      The easiest and recommended way to install GitHub CLI on macOS is through Homebrew.<\/p>\n\n\n\n
      This method supports both Intel Macs and Apple Silicon devices.<\/p>\n\n\n\n
      Step 1: Open Terminal<\/h2>\n\n\n\n
      Open the Terminal application:<\/p>\n\n\n\n
      Applications \u2192 Utilities \u2192 Terminal<\/p>\n\n\n\n
      Alternatively, press Command + Space<\/code>, search for Terminal, and open it.<\/p>\n\n\n\n
      Step 2: Check macOS Version<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      sw_vers<\/code><\/span><\/pre>\n\n\n
      Example:<\/p>\n\n\n
      ProductName<\/span>: macOS\nProductVersion<\/span>: 26.x\nBuildVersion<\/span>: ...<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
      Check your processor architecture:<\/p>\n\n\n
      uname -m<\/code><\/span><\/pre>\n\n\n
      For Apple Silicon, the output is:<\/p>\n\n\n
      arm64<\/code><\/span><\/pre>\n\n\n
      For Intel Macs:<\/p>\n\n\n
      x86_64<\/code><\/span><\/pre>\n\n\n
      Homebrew selects the appropriate compatible package for your setup.<\/p>\n\n\n\n
      Step 3: Check Whether Homebrew Is Installed<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      brew --version<\/code><\/span><\/pre>\n\n\n
      If Homebrew is installed, the version information will appear.<\/p>\n\n\n\n
      If you receive:<\/p>\n\n\n
      zsh<\/span>: command not found: brew<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
      Homebrew may not be installed or configured in your shell.<\/p>\n\n\n\n
      Install Homebrew using the official installer:<\/p>\n\n\n
      \/bin\/bash -c \"$(curl -fsSL https:\/\/raw.githubusercontent.com\/Homebrew\/install\/HEAD\/install.sh)\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Review the script and its permissions before running it.<\/p>\n\n\n\n
      After installation, follow any instructions printed by the installer to configure the Homebrew shell environment.<\/p>\n\n\n\n
      Verify:<\/p>\n\n\n
      brew --version<\/code><\/span><\/pre>\n\n\n
      Step 4: Update Homebrew<\/h2>\n\n\n\n
      Before installing GitHub CLI, refresh Homebrew:<\/p>\n\n\n
      brew update<\/code><\/span><\/pre>\n\n\n
      This updates Homebrew’s package metadata.<\/p>\n\n\n\n
      Step 5: Install GitHub CLI<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      brew install gh<\/code><\/span><\/pre>\n\n\n
      Homebrew downloads and installs GitHub CLI.<\/p>\n\n\n\n
      The executable becomes available through your configured Homebrew command path.<\/p>\n\n\n\n
      Step 6: Verify GitHub CLI Installation<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n\n
      Example output:<\/p>\n\n\n
      gh version 2.<\/span>x.x\nhttps<\/span>:\/\/github.com\/cli\/cli\/releases\/tag\/v2.x.x<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Your actual version may be newer.<\/p>\n\n\n\n
      Display available commands:<\/p>\n\n\n
      gh --help<\/code><\/span><\/pre>\n\n\n
      If GitHub CLI displays command information, the installation has succeeded.<\/p>\n\n\n\n
      Step 7: Find the GitHub CLI Executable<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      which gh<\/code><\/span><\/pre>\n\n\n
      Or:<\/p>\n\n\n
      command -v gh<\/code><\/span><\/pre>\n\n\n
      For Apple Silicon Macs, the path commonly looks like:<\/p>\n\n\n
      \/opt\/homebrew\/bin\/gh<\/code><\/span><\/pre>\n\n\n
      For Intel Macs:<\/p>\n\n\n
      \/usr\/local\/bin\/gh<\/code><\/span><\/pre>\n\n\n
      The actual location depends on your Homebrew configuration.<\/p>\n\n\n\n
      Step 8: Verify the Homebrew Package<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      brew list<\/span> --versions gh<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      You can also inspect package information:<\/p>\n\n\n
      brew info gh<\/code><\/span><\/pre>\n\n\n
      GitHub CLI is now successfully installed on macOS.<\/strong><\/p>\n\n\n\n
      Alternative: Install GitHub CLI Without Homebrew<\/h3>\n\n\n\n
      If you do not want to use Homebrew, download the official macOS binary or installer from:<\/p>\n\n\n\n
      \nhttps:\/\/github.com\/cli\/cli\/releases\/latest\n<\/div><\/figure>\n\n\n\n
      Select the package matching your processor architecture and follow the installation instructions included with that release.<\/p>\n\n\n\n
      For routine macOS development, Homebrew is generally the simplest option.<\/p>\n\n\n\n
      \n\n\n\n
      5. How to Install GitHub CLI on Windows 10 and Windows 11<\/h1>\n\n\n\n
      GitHub officially supports installing GitHub CLI on Windows through WinGet.<\/p>\n\n\n\n
      WinGet is Microsoft’s Windows Package Manager.<\/p>\n\n\n\n
      Method 1: Install GitHub CLI Using WinGet (Recommended)<\/h2>\n\n\n\n
      Step 1: Open PowerShell<\/h3>\n\n\n\n
      Open Windows PowerShell or PowerShell 7.<\/p>\n\n\n\n
      You can search for PowerShell from the Windows Start menu.<\/p>\n\n\n\n
      Step 2: Check Whether WinGet Is Installed<\/h3>\n\n\n\n
      Execute:<\/p>\n\n\n
      winget --version<\/code><\/span><\/pre>\n\n\n
      If available, WinGet displays its installed version.<\/p>\n\n\n\n
      If Windows reports that winget<\/code> is not recognized, install or update App Installer<\/strong> through Microsoft’s supported distribution method.<\/p>\n\n\n\n
      WinGet is included in modern supported Windows environments through App Installer.<\/p>\n\n\n\n
      Step 3: Search for GitHub CLI<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      winget<\/span> search<\/span> GitHub<\/span>.cli<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      The search should return GitHub CLI.<\/p>\n\n\n\n
      The package identifier is:<\/p>\n\n\n
      GitHub<\/span>.cli<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 4: Install GitHub CLI<\/h3>\n\n\n\n
      Execute:<\/p>\n\n\n
      winget<\/span> install<\/span> --id<\/span> GitHub<\/span>.cli<\/span> --source<\/span> winget<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      WinGet downloads the GitHub CLI package and starts its installation.<\/p>\n\n\n\n
      Accept any required package agreements and installation prompts.<\/p>\n\n\n\n
      Step 5: Open a New Terminal<\/h3>\n\n\n\n
      After installation, close the existing Windows Terminal or PowerShell window and open a new one.<\/p>\n\n\n\n
      Important:<\/strong> The installer updates the Windows PATH. When using Windows Terminal, a completely new window may be needed; opening only a new tab may not refresh the environment.<\/p>\n\n\n\n
      Step 6: Verify the Installation<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n\n
      Display help:<\/p>\n\n\n
      gh --help<\/code><\/span><\/pre>\n\n\n
      Step 7: Locate the Executable<\/h3>\n\n\n\n
      Execute:<\/p>\n\n\n
      Get-Command gh<\/code><\/span><\/pre>\n\n\n
      Or:<\/p>\n\n\n
      where<\/span>.exe<\/span> gh<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      These commands identify the executable Windows is using.<\/p>\n\n\n\n
      Step 8: Confirm the Installed Package<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      winget<\/span> list<\/span> --id<\/span> GitHub<\/span>.cli<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      If the package appears, GitHub CLI is installed and managed through WinGet.<\/p>\n\n\n\n
      GitHub CLI is ready on Windows.<\/strong><\/p>\n\n\n\n
      Method 2: Install GitHub CLI Using Scoop<\/h2>\n\n\n\n
      If you already use the Scoop package manager, you can install GitHub CLI through Scoop.<\/p>\n\n\n\n
      Execute:<\/p>\n\n\n
      scoop install gh<\/code><\/span><\/pre>\n\n\n
      Verify:<\/p>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n\n
      To upgrade later:<\/p>\n\n\n
      scoop update gh<\/code><\/span><\/pre>\n\n\n
      This method assumes Scoop is already installed.<\/p>\n\n\n\n
      Method 3: Install GitHub CLI Using Chocolatey<\/h2>\n\n\n\n
      For systems that already use Chocolatey, run:<\/p>\n\n\n
      choco install gh -y<\/code><\/span><\/pre>\n\n\n
      Verify:<\/p>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n\n
      To upgrade:<\/p>\n\n\n
      choco upgrade gh -y<\/code><\/span><\/pre>\n\n\n
      The Scoop and Chocolatey package distributions are community-supported installation alternatives.<\/p>\n\n\n\n
      Method 4: Install GitHub CLI Using an MSI Installer<\/h2>\n\n\n\n
      If WinGet is unavailable, you can install GitHub CLI using the official MSI package.<\/p>\n\n\n\n
      Step 1: Download the Installer<\/h3>\n\n\n\n
      Visit:<\/p>\n\n\n\n
      \nhttps:\/\/github.com\/cli\/cli\/releases\/latest\n<\/div><\/figure>\n\n\n\n
      Download the Windows MSI installer matching your architecture.<\/p>\n\n\n\n
      An x64 installer normally follows a naming convention similar to:<\/p>\n\n\n
      gh_<version<\/span>><\/span>_windows_amd64.msi<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
      The actual filename depends on the release.<\/p>\n\n\n\n
      Step 2: Run the Installer<\/h3>\n\n\n\n
      Double-click the downloaded MSI package.<\/p>\n\n\n\n
      Follow the installation wizard.<\/p>\n\n\n\n
      Administrator permissions may be required depending on the installation settings and system policies.<\/p>\n\n\n\n
      Step 3: Reopen PowerShell<\/h3>\n\n\n\n
      Open a new PowerShell window and execute:<\/p>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n\n
      Then:<\/p>\n\n\n
      gh --help<\/code><\/span><\/pre>\n\n\n
      If both commands work, the installation was successful.<\/p>\n\n\n\n
      \n\n\n\n
      6. How to Install GitHub CLI on Ubuntu and Debian Linux<\/h1>\n\n\n\n
      GitHub provides an official APT repository for Ubuntu, Debian, and compatible distributions.<\/p>\n\n\n\n
      Using this repository is recommended because distribution-maintained packages can lag behind official releases.<\/p>\n\n\n\n
      Step 1: Check Your Linux Distribution<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      cat \/etc\/os-release<\/code><\/span><\/pre>\n\n\n
      Check CPU architecture:<\/p>\n\n\n
      uname -m<\/code><\/span><\/pre>\n\n\n
      Example output:<\/p>\n\n\n
      x86_64<\/code><\/span><\/pre>\n\n\n
      Or:<\/p>\n\n\n
      aarch64<\/code><\/span><\/pre>\n\n\n
      Step 2: Update Package Information<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      sudo apt update<\/code><\/span><\/pre>\n\n\n
      Step 3: Install Required Utilities<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      sudo apt install -y wget ca-certificates<\/code><\/span><\/pre>\n\n\n
      These packages provide file downloading and trusted CA certificate support.<\/p>\n\n\n\n
      Step 4: Create the APT Keyring Directory<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      sudo mkdir -p -m 755 \/etc\/apt\/keyrings<\/code><\/span><\/pre>\n\n\n
      Step 5: Download GitHub CLI’s Repository Signing Key<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      tmp_keyring=$(mktemp)\n\nwget -q -O \"$tmp_keyring\"<\/span> \\\n  https<\/span>:\/\/cli.github.com\/packages\/githubcli-archive-keyring.gpg<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Install the downloaded keyring:<\/p>\n\n\n
      sudo install -m 644<\/span> \"$tmp_keyring\"<\/span> \\\n  \/etc\/apt\/keyrings\/githubcli-archive-keyring.gpg<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Remove the temporary download:<\/p>\n\n\n
      rm -f \"$tmp_keyring\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This registers the repository signing key for GitHub CLI.<\/p>\n\n\n\n
      Security note:<\/strong> GitHub CLI rotated its Linux repository signing keys effective September 5, 2026. If you have an older repository configuration, update the keyring using the current official documentation rather than disabling APT signature verification.<\/p>\n\n\n\n
      GitHub publishes the current signing key fingerprints in its Linux installation guide.<\/p>\n\n\n\n
      Step 6: Add the GitHub CLI APT Repository<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      echo<\/span> \"deb [arch=$(dpkg --print-architecture) signed-by=\/etc\/apt\/keyrings\/githubcli-archive-keyring.gpg] https:\/\/cli.github.com\/packages stable main\"<\/span> \\\n  | sudo tee \/etc\/apt\/sources.list<\/span>.d\/github-cli.list<\/span> > \/dev\/null<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This creates an APT source entry for GitHub CLI.<\/p>\n\n\n\n
      Step 7: Update Package Metadata<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      sudo apt update<\/code><\/span><\/pre>\n\n\n
      APT refreshes the package metadata, including the GitHub CLI repository.<\/p>\n\n\n\n
      Step 8: Install GitHub CLI<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      sudo apt install -y gh<\/code><\/span><\/pre>\n\n\n
      APT downloads and installs the official GitHub CLI package.<\/p>\n\n\n\n
      Step 9: Verify Installation<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n\n
      Display help:<\/p>\n\n\n
      gh --help<\/code><\/span><\/pre>\n\n\n
      Locate the executable:<\/p>\n\n\n
      command -v gh<\/code><\/span><\/pre>\n\n\n
      Check the package:<\/p>\n\n\n
      dpkg -l gh<\/code><\/span><\/pre>\n\n\n
      Step 10: Inspect the Package Source<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      apt-cache policy gh<\/code><\/span><\/pre>\n\n\n
      This displays the installed and candidate versions and helps identify the repository from which APT obtained the package.<\/p>\n\n\n\n
      GitHub CLI is successfully installed on Ubuntu or Debian.<\/strong><\/p>\n\n\n\n
      \n\n\n\n
      7. How to Install GitHub CLI on Fedora, RHEL, and CentOS<\/h1>\n\n\n\n
      GitHub maintains official RPM packages that can be installed using DNF.<\/p>\n\n\n\n
      The commands differ slightly between DNF4 and DNF5.<\/p>\n\n\n\n
      Step 1: Check Your Linux Version<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      cat \/etc\/os-release<\/code><\/span><\/pre>\n\n\n
      Check the package manager version:<\/p>\n\n\n
      dnf --version<\/code><\/span><\/pre>\n\n\n
      If your system uses DNF5, follow Method 1.<\/p>\n\n\n\n
      If it uses DNF4, follow Method 2.<\/p>\n\n\n\n
      Method 1: Install GitHub CLI Using DNF5<\/h2>\n\n\n\n
      Step 1: Install DNF5 Plugins<\/h3>\n\n\n
      sudo dnf install -y dnf5-plugins<\/code><\/span><\/pre>\n\n\n
      Step 2: Add the Official GitHub CLI Repository<\/h3>\n\n\n
      sudo dnf config-manager addrepo \\\n  --from<\/span>-repofile=https:\/\/cli.github.com\/packages\/rpm\/gh-cli.repo<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 3: Install GitHub CLI<\/h3>\n\n\n
      sudo dnf install -y gh<\/code><\/span><\/pre>\n\n\n
      Step 4: Verify Installation<\/h3>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n\n
      Check the package:<\/p>\n\n\n
      rpm -q gh<\/code><\/span><\/pre>\n\n\n
      Method 2: Install GitHub CLI Using DNF4<\/h2>\n\n\n\n
      Step 1: Install the Repository Management Plugin<\/h3>\n\n\n
      sudo dnf install -y 'dnf-command(config-manager)'<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 2: Add the GitHub CLI RPM Repository<\/h3>\n\n\n
      sudo dnf config-manager --add-repo \\\n  https<\/span>:\/\/cli.github.com\/packages\/rpm\/gh-cli.repo<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 3: Install GitHub CLI<\/h3>\n\n\n
      sudo dnf install -y gh<\/code><\/span><\/pre>\n\n\n
      Step 4: Verify Installation<\/h3>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n
      gh --help<\/code><\/span><\/pre>\n\n\n
      Alternative: Fedora Community Repository<\/h3>\n\n\n\n
      Fedora also provides a community-maintained package.<\/p>\n\n\n\n
      You can install it with:<\/p>\n\n\n
      sudo dnf install gh<\/code><\/span><\/pre>\n\n\n
      However, the GitHub-maintained repository is preferable when you require releases published directly by the GitHub CLI maintainers.<\/p>\n\n\n\n
      \n\n\n\n
      8. Install GitHub CLI on Amazon Linux<\/h1>\n\n\n\n
      For Amazon Linux 2, GitHub documents installation through its official RPM repository.<\/p>\n\n\n\n
      Step 1: Check the Operating System<\/h2>\n\n\n
      cat \/etc\/os-release<\/code><\/span><\/pre>\n\n\n
      Confirm that your system is Amazon Linux 2 before using these YUM-specific instructions.<\/p>\n\n\n\n
      Step 2: Install YUM Repository Utilities<\/h2>\n\n\n
      sudo yum install -y yum-utils<\/code><\/span><\/pre>\n\n\n
      Step 3: Add the GitHub CLI Repository<\/h2>\n\n\n
      sudo yum-config-manager --add-repo \\\n  https<\/span>:\/\/cli.github.com\/packages\/rpm\/gh-cli.repo<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 4: Install GitHub CLI<\/h2>\n\n\n
      sudo yum install -y gh<\/code><\/span><\/pre>\n\n\n
      Step 5: Verify Installation<\/h2>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n
      command -v gh<\/code><\/span><\/pre>\n\n\n
      For Amazon Linux 2023, check the supported DNF repository instructions appropriate to the installed DNF version.<\/p>\n\n\n\n
      \n\n\n\n
      9. Install GitHub CLI on Other Linux Distributions<\/h1>\n\n\n\n
      GitHub CLI is also available on several additional distributions.<\/p>\n\n\n\n
      Arch Linux<\/h3>\n\n\n
      sudo pacman -S github-cli<\/code><\/span><\/pre>\n\n\n
      Alpine Linux<\/h3>\n\n\n
      sudo apk add github-cli<\/code><\/span><\/pre>\n\n\n
      openSUSE and SUSE Linux<\/h3>\n\n\n\n
      Add the official RPM repository:<\/p>\n\n\n
      sudo zypper addrepo \\\n  https<\/span>:\/\/cli.github.com\/packages\/rpm\/gh-cli.repo<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Refresh repositories:<\/p>\n\n\n
      sudo zypper ref<\/code><\/span><\/pre>\n\n\n
      Install GitHub CLI:<\/p>\n\n\n
      sudo zypper install gh<\/code><\/span><\/pre>\n\n\n
      Linux with Homebrew<\/h3>\n\n\n\n
      If Homebrew is already installed:<\/p>\n\n\n
      brew install gh<\/code><\/span><\/pre>\n\n\n
      Alternative: Download Standalone Binaries<\/h3>\n\n\n\n
      Official GitHub CLI binaries are also available from:<\/p>\n\n\n\n
      \nhttps:\/\/github.com\/cli\/cli\/releases\/latest\n<\/div><\/figure>\n\n\n\n
      Download the archive matching your operating system and processor architecture.<\/p>\n\n\n\n
      Verify the archive’s authenticity before extracting and installing it.<\/p>\n\n\n\n
      \n\n\n\n
      10. How to Authenticate GitHub CLI<\/h1>\n\n\n\n
      After installing GitHub CLI, you need to authenticate with your GitHub account to access private repositories and perform authorized GitHub operations.<\/p>\n\n\n\n
      Step 1: Start GitHub Authentication<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      gh auth login<\/code><\/span><\/pre>\n\n\n
      The CLI starts an interactive authentication process.<\/p>\n\n\n\n
      You may be prompted with options similar to:<\/p>\n\n\n
      ? Where do<\/span> you use<\/span> GitHub<\/span>?\n> GitHub<\/span>.com<\/span>\n  Other<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Select GitHub.com unless you use a GitHub Enterprise host.<\/p>\n\n\n\n
      Step 2: Choose Your Git Protocol<\/h2>\n\n\n\n
      GitHub CLI asks which protocol you want to use for Git operations.<\/p>\n\n\n\n
      Typical choices are:<\/p>\n\n\n
      HTTPS\nSSH<\/code><\/span><\/pre>\n\n\n
      For beginners, HTTPS is often easier to configure.<\/p>\n\n\n\n
      SSH is useful if you already manage SSH keys for Git operations.<\/p>\n\n\n\n
      Step 3: Authenticate Through Your Browser<\/h2>\n\n\n\n
      Select browser-based authentication.<\/p>\n\n\n\n
      Alternatively, start the browser flow directly:<\/p>\n\n\n
      gh auth login --web<\/code><\/span><\/pre>\n\n\n
      To copy the temporary authentication code to your clipboard:<\/p>\n\n\n
      gh auth login --web --clipboard<\/code><\/span><\/pre>\n\n\n
      The CLI initiates the GitHub device authentication process.<\/p>\n\n\n\n
      If required, visit:<\/p>\n\n\n\n
      \nhttps:\/\/github.com\/login\/device\n<\/div><\/figure>\n\n\n\n
      Enter the one-time code displayed in your terminal and approve the authorization.<\/p>\n\n\n\n
      Step 4: Verify GitHub Authentication<\/h2>\n\n\n\n
      After login, execute:<\/p>\n\n\n
      gh auth status<\/code><\/span><\/pre>\n\n\n
      This shows the configured authentication state for known GitHub hosts.<\/p>\n\n\n\n
      It can display the active account, authentication method, and stored credential information without revealing the token by default.<\/p>\n\n\n\n
      Step 5: Configure Git Credential Integration<\/h2>\n\n\n\n
      For HTTPS-based Git authentication, execute:<\/p>\n\n\n
      gh auth setup-git<\/code><\/span><\/pre>\n\n\n
      This configures Git to use GitHub CLI as a credential helper for authenticated hosts.<\/p>\n\n\n\n
      It can simplify authenticated Git operations such as:<\/p>\n\n\n
      git clone<\/span>\ngit fetch\ngit pull\ngit push<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      When using SSH, make sure your SSH key is correctly configured and authorized for GitHub.<\/p>\n\n\n\n
      Step 6: Confirm Everything Works<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      gh repo view cli\/cli<\/code><\/span><\/pre>\n\n\n
      This displays information about GitHub CLI’s own public repository.<\/p>\n\n\n\n
      If repository details appear, the CLI can successfully communicate with GitHub.<\/p>\n\n\n\n
      \n\n\n\n
      11. Essential GitHub CLI Commands for Beginners<\/h1>\n\n\n\n
      After installing and authenticating GitHub CLI, try these commands.<\/p>\n\n\n\n
      Check CLI Version<\/h2>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n\n
      Check Authentication Status<\/h2>\n\n\n
      gh auth status<\/code><\/span><\/pre>\n\n\n
      List Your Repositories<\/h2>\n\n\n
      gh repo list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      To display more results:<\/p>\n\n\n
      gh repo list<\/span> --limit 50<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      View a Repository<\/h2>\n\n\n
      gh repo view cli\/cli<\/code><\/span><\/pre>\n\n\n
      Clone a Repository<\/h2>\n\n\n
      gh repo clone<\/span> cli\/cli<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This creates a local copy of the repository in your current directory.<\/p>\n\n\n\n
      List GitHub Issues<\/h2>\n\n\n\n
      Within a GitHub repository:<\/p>\n\n\n
      gh issue list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Or specify the repository explicitly:<\/p>\n\n\n
      gh issue list<\/span> --repo cli\/cli<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      List Pull Requests<\/h2>\n\n\n
      gh pr list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      For a specific repository:<\/p>\n\n\n
      gh pr list<\/span> --repo cli\/cli<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Check Pull Request Status<\/h2>\n\n\n
      gh pr status<\/code><\/span><\/pre>\n\n\n
      Create a Pull Request<\/h2>\n\n\n\n
      When you are working on a branch with changes ready for review:<\/p>\n\n\n
      gh pr create<\/code><\/span><\/pre>\n\n\n
      To prefill the title and description from commits:<\/p>\n\n\n
      gh pr create --fill<\/code><\/span><\/pre>\n\n\n
      This operation creates a real pull request after any required prompts and permissions checks.<\/p>\n\n\n\n
      View GitHub Actions Workflows<\/h2>\n\n\n
      gh workflow list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      View GitHub Actions Runs<\/h2>\n\n\n
      gh run list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      List GitHub Releases<\/h2>\n\n\n
      gh release list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Execute a GitHub API Request<\/h2>\n\n\n\n
      For example, retrieve the authenticated user’s information:<\/p>\n\n\n
      gh api user<\/code><\/span><\/pre>\n\n\n
      This returns JSON data from the GitHub API.<\/p>\n\n\n\n
      Log Out<\/h2>\n\n\n
      gh auth logout<\/code><\/span><\/pre>\n\n\n
      You can also target GitHub.com explicitly:<\/p>\n\n\n
      gh<\/span> auth<\/span> logout<\/span> --hostname<\/span> github<\/span>.com<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n\n\n\n
      12. Configure GitHub CLI Settings<\/h1>\n\n\n\n
      GitHub CLI provides configuration commands for customizing its behavior.<\/p>\n\n\n\n
      View Current Configuration<\/h2>\n\n\n
      gh config list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Configure HTTPS for Git Operations<\/h2>\n\n\n
      gh config set<\/span> git_protocol https --host github.com<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Configure SSH for Git Operations<\/h2>\n\n\n
      gh config set<\/span> git_protocol ssh --host github.com<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Use SSH only after ensuring that the appropriate SSH keys are configured.<\/p>\n\n\n\n
      Configure VS Code as the Default Editor<\/h2>\n\n\n
      gh config set<\/span> editor \"code --wait\"<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This requires the VS Code code<\/code> command to be available in PATH.<\/p>\n\n\n\n
      Configure Vim as the Default Editor<\/h2>\n\n\n
      gh config set<\/span> editor vim<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Check a Configuration Value<\/h2>\n\n\n
      gh config get<\/span> git_protocol<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Configuration settings allow you to tailor GitHub CLI to your preferred development workflow.<\/p>\n\n\n\n
      \n\n\n\n
      13. How to Update GitHub CLI<\/h1>\n\n\n\n
      GitHub CLI receives ongoing updates, so keeping your installation current is recommended.<\/p>\n\n\n\n
      The upgrade procedure depends on your installation method.<\/p>\n\n\n\n
      macOS<\/h2>\n\n\n
      brew update\nbrew upgrade gh<\/code><\/span><\/pre>\n\n\n
      Windows \u2014 WinGet<\/h2>\n\n\n
      winget<\/span> upgrade<\/span> --id<\/span> GitHub<\/span>.cli<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Windows \u2014 Scoop<\/h2>\n\n\n
      scoop update gh<\/code><\/span><\/pre>\n\n\n
      Windows \u2014 Chocolatey<\/h2>\n\n\n
      choco upgrade gh<\/code><\/span><\/pre>\n\n\n
      Ubuntu\/Debian<\/h2>\n\n\n
      sudo apt update\nsudo apt install gh<\/code><\/span><\/pre>\n\n\n
      Fedora\/RHEL\/CentOS<\/h2>\n\n\n
      sudo dnf update gh<\/code><\/span><\/pre>\n\n\n
      Amazon Linux 2<\/h2>\n\n\n
      sudo yum update gh<\/code><\/span><\/pre>\n\n\n
      Arch Linux<\/h2>\n\n\n
      sudo pacman -Syu<\/code><\/span><\/pre>\n\n\n
      After upgrading, always verify:<\/p>\n\n\n
      gh --version<\/code><\/span><\/pre>\n\n\n
      For automated production environments, consider pinning a tested GitHub CLI release rather than automatically updating to every newly published version.<\/p>\n\n\n\n
      \n\n\n\n
      14. Troubleshooting GitHub CLI Installation Errors<\/h1>\n\n\n\n
      The following table covers common installation and authentication issues.<\/p>\n\n\n\n
      Error or symptom<\/th>Likely cause<\/th>Troubleshooting<\/th><\/tr>
      gh: command not found<\/code><\/td>CLI missing or PATH not configured<\/td>Verify installation and executable path<\/td><\/tr>
      zsh: command not found: brew<\/code><\/td>Homebrew not installed or not on PATH<\/td>Install\/configure Homebrew<\/td><\/tr>
      gh is not recognized<\/code><\/td>Windows PATH not refreshed<\/td>Open a new terminal and check PATH<\/td><\/tr>
      winget is not recognized<\/code><\/td>WinGet unavailable<\/td>Install or update Windows App Installer<\/td><\/tr>
      Unable to locate package gh<\/code><\/td>APT repository missing or outdated<\/td>Check official repository and run apt update<\/code><\/td><\/tr>
      NO_PUBKEY<\/code> or GPG error<\/td>Missing, outdated, or incorrect repository signing key<\/td>Reinstall the current official keyring<\/td><\/tr>
      exec format error<\/code><\/td>Incorrect binary architecture<\/td>Download the appropriate binary<\/td><\/tr>
      HTTP 401<\/code><\/td>Authentication missing or invalid<\/td>Check gh auth status<\/code> and reauthenticate<\/td><\/tr>
      HTTP 403<\/code><\/td>Insufficient permissions or policy restrictions<\/td>Review account, token, and repository access<\/td><\/tr>
      Permission denied (publickey)<\/code><\/td>SSH authentication failure<\/td>Verify SSH key and remote configuration<\/td><\/tr>
      Git push authentication fails<\/td>Git credential helper or remote configuration issue<\/td>Inspect remote URL and configure gh auth setup-git<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      Troubleshooting 1: gh Command Not Found on macOS<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      command -v gh<\/code><\/span><\/pre>\n\n\n
      Verify the Homebrew package:<\/p>\n\n\n
      brew list<\/span> --versions gh<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Check the PATH:<\/p>\n\n\n
      echo<\/span> \"$PATH\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      If the package is installed but the executable is not available, confirm Homebrew is properly configured in the shell.<\/p>\n\n\n\n
      Troubleshooting 2: gh Not Recognized on Windows<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      Get-Command gh<\/code><\/span><\/pre>\n\n\n
      Check PATH:<\/p>\n\n\n
      $env:Path<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      If GitHub CLI was just installed through MSI or WinGet, close Windows Terminal completely and open it again.<\/p>\n\n\n\n
      If the command remains unavailable, inspect the installer status and the actual location of gh.exe<\/code>.<\/p>\n\n\n\n
      Troubleshooting 3: APT Cannot Locate the gh Package<\/h2>\n\n\n\n
      First check the configured repository:<\/p>\n\n\n
      cat \/etc\/apt\/sources.list<\/span>.d\/github-cli.list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Refresh metadata:<\/p>\n\n\n
      sudo apt update<\/code><\/span><\/pre>\n\n\n
      Check package availability:<\/p>\n\n\n
      apt-cache policy gh<\/code><\/span><\/pre>\n\n\n
      If the official GitHub CLI repository is missing, configure it using the instructions in Section 6.<\/p>\n\n\n\n
      If the package repository reports a signature verification problem, correct the repository signing key instead of bypassing package signature checks.<\/p>\n\n\n\n
      Troubleshooting 4: GitHub CLI Authentication Failed<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      gh auth status<\/code><\/span><\/pre>\n\n\n
      If authentication is invalid or missing, repeat login:<\/p>\n\n\n
      gh auth login<\/code><\/span><\/pre>\n\n\n
      For browser-based authentication:<\/p>\n\n\n
      gh auth login --web<\/code><\/span><\/pre>\n\n\n
      If using GitHub Enterprise, specify the correct host:<\/p>\n\n\n
      gh<\/span> auth<\/span> login<\/span> --hostname<\/span> github<\/span>.example<\/span>.com<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Replace github.example.com<\/code> with your organization’s actual GitHub Enterprise hostname.<\/p>\n\n\n\n
      Troubleshooting 5: SSH Permission Denied<\/h2>\n\n\n\n
      Example:<\/p>\n\n\n
      git@github.com<\/span>: Permission denied (publickey).<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
      This typically indicates an SSH authentication problem rather than a GitHub CLI installation issue.<\/p>\n\n\n\n
      Inspect your SSH connection:<\/p>\n\n\n
      ssh<\/span> -T<\/span> git<\/span>@github<\/span>.com<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Check the Git remote:<\/p>\n\n\n
      git remote -v<\/code><\/span><\/pre>\n\n\n
      If your Git remote uses HTTPS instead, you can configure GitHub CLI as the credential helper:<\/p>\n\n\n
      gh auth setup-git<\/code><\/span><\/pre>\n\n\n
      For SSH-based operations, verify that a valid SSH key is registered with your GitHub account.<\/p>\n\n\n\n
      Troubleshooting 6: Multiple Versions of gh Installed<\/h2>\n\n\n\n
      On macOS or Linux:<\/p>\n\n\n
      type -a gh<\/code><\/span><\/pre>\n\n\n
      On Windows:<\/p>\n\n\n
      Get-Command gh -All<\/code><\/span><\/pre>\n\n\n
      This helps identify multiple installations.<\/p>\n\n\n\n
      For example, one executable may come from a package manager and another from a manually downloaded binary.<\/p>\n\n\n\n
      Make sure your PATH resolves to the intended installation.<\/p>\n\n\n\n
      \n\n\n\n
      15. How to Uninstall GitHub CLI<\/h1>\n\n\n\n
      If you no longer need GitHub CLI, remove it using the package manager that installed it.<\/p>\n\n\n\n
      macOS<\/h2>\n\n\n
      brew uninstall gh<\/code><\/span><\/pre>\n\n\n
      Windows \u2014 WinGet<\/h2>\n\n\n
      winget<\/span> uninstall<\/span> --id<\/span> GitHub<\/span>.cli<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Windows \u2014 Scoop<\/h2>\n\n\n
      scoop uninstall gh<\/code><\/span><\/pre>\n\n\n
      Windows \u2014 Chocolatey<\/h2>\n\n\n
      choco uninstall gh<\/code><\/span><\/pre>\n\n\n
      Ubuntu\/Debian<\/h2>\n\n\n
      sudo apt remove gh<\/code><\/span><\/pre>\n\n\n
      Fedora\/RHEL\/CentOS<\/h2>\n\n\n
      sudo dnf remove gh<\/code><\/span><\/pre>\n\n\n
      Amazon Linux 2<\/h2>\n\n\n
      sudo yum remove gh<\/code><\/span><\/pre>\n\n\n
      Arch Linux<\/h2>\n\n\n
      sudo pacman -R github-cli<\/code><\/span><\/pre>\n\n\n
      Removing the executable does not necessarily remove all stored configuration or credentials.<\/p>\n\n\n\n
      If you want to disconnect your GitHub account before uninstalling, run:<\/p>\n\n\n
      gh auth logout<\/code><\/span><\/pre>\n\n\n
      Be aware that logging out of GitHub CLI does not automatically revoke all previously issued credentials on the GitHub server. Revoke access through GitHub account settings if needed.<\/p>\n\n\n\n
      \n\n\n\n
      16. GitHub CLI Installation Cheat Sheet<\/h1>\n\n\n\n
      Operating system<\/th>Recommended command<\/th><\/tr>
      macOS Intel<\/td>brew install gh<\/code><\/td><\/tr>
      macOS Apple Silicon<\/td>brew install gh<\/code><\/td><\/tr>
      Windows 10\/11<\/td>winget install --id GitHub.cli<\/code><\/td><\/tr>
      Windows with Scoop<\/td>scoop install gh<\/code><\/td><\/tr>
      Windows with Chocolatey<\/td>choco install gh<\/code><\/td><\/tr>
      Ubuntu\/Debian<\/td>Configure official repository, then sudo apt install gh<\/code><\/td><\/tr>
      Fedora with DNF<\/td>Configure official repository, then sudo dnf install gh<\/code><\/td><\/tr>
      RHEL\/CentOS<\/td>Configure official RPM repository, then sudo dnf install gh<\/code><\/td><\/tr>
      Amazon Linux 2<\/td>Configure official RPM repository, then sudo yum install gh<\/code><\/td><\/tr>
      Arch Linux<\/td>sudo pacman -S github-cli<\/code><\/td><\/tr>
      Alpine Linux<\/td>sudo apk add github-cli<\/code><\/td><\/tr>
      openSUSE<\/td>Configure official repository, then sudo zypper install gh<\/code><\/td><\/tr>
      Verify installation<\/td>gh --version<\/code><\/td><\/tr>
      Authenticate<\/td>gh auth login<\/code><\/td><\/tr>
      Check authentication<\/td>gh auth status<\/code><\/td><\/tr>
      Configure Git credentials<\/td>gh auth setup-git<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n
      17. Frequently Asked Questions<\/h1>\n\n\n\n
      Q1. Is GitHub CLI free?<\/h3>\n\n\n\n
      Yes. GitHub CLI is free and open source.<\/p>\n\n\n\n
      Some operations may interact with GitHub features or resources that have separate usage limits or billing requirements.<\/p>\n\n\n\n
      Q2. Do I need Git installed to use GitHub CLI?<\/h3>\n\n\n\n
      GitHub CLI can be installed independently of Git.<\/p>\n\n\n\n
      However, normal Git repository operations require Git, so installing both is recommended.<\/p>\n\n\n\n
      Q3. Can GitHub CLI be installed on Apple Silicon Macs?<\/h3>\n\n\n\n
      Yes. GitHub CLI supports Apple Silicon through compatible macOS packages, including Homebrew.<\/p>\n\n\n\n
      Q4. Does GitHub CLI work on Windows 11?<\/h3>\n\n\n\n
      Yes. GitHub CLI supports Windows and can be installed using WinGet or an official MSI installer.<\/p>\n\n\n\n
      Q5. Can I use GitHub CLI without opening a browser?<\/h3>\n\n\n\n
      Yes, certain operations work without browser interaction.<\/p>\n\n\n\n
      For authentication on a workstation, the standard browser-based authorization is usually convenient. For automation, GitHub CLI supports suitable authentication tokens supplied through environment variables.<\/p>\n\n\n\n
      Q6. Can GitHub CLI be used in GitHub Actions?<\/h3>\n\n\n\n
      Yes. GitHub CLI is preinstalled on GitHub-hosted Actions runners.<\/p>\n\n\n\n
      For workflows that need GitHub authentication, configure the appropriate token and permissions.<\/p>\n\n\n\n
      For example, within a GitHub Actions workflow:<\/p>\n\n\n
      env:\n  GH_TOKEN: ${{ github.token }}<\/code><\/span><\/pre>\n\n\n
      The workflow’s permissions must allow the requested operations.<\/p>\n\n\n\n
      Q7. Can GitHub CLI manage private repositories?<\/h3>\n\n\n\n
      Yes, provided the authenticated identity has access to those repositories and sufficient permissions for the requested commands.<\/p>\n\n\n\n
      Q8. Can I use GitHub CLI with multiple GitHub accounts?<\/h3>\n\n\n\n
      Yes. GitHub CLI supports managing authenticated accounts and switching the active account.<\/p>\n\n\n\n
      You can inspect the authentication state:<\/p>\n\n\n
      gh auth status<\/code><\/span><\/pre>\n\n\n
      And switch among configured accounts:<\/p>\n\n\n
      gh auth switch<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Q9. Can GitHub CLI connect to GitHub Enterprise?<\/h3>\n\n\n\n
      Yes. GitHub CLI supports GitHub.com, GitHub Enterprise Cloud, and supported GitHub Enterprise Server versions.<\/p>\n\n\n\n
      You can specify a host with:<\/p>\n\n\n
      gh<\/span> auth<\/span> login<\/span> --hostname<\/span> github<\/span>.example<\/span>.com<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Q10. Is GitHub CLI better than using the GitHub website?<\/h3>\n\n\n\n
      Neither replaces the other completely.<\/p>\n\n\n\n
      GitHub CLI is particularly useful for repetitive operations, terminal-centric development, scripting, CI\/CD, and automation.<\/p>\n\n\n\n
      The web interface remains valuable for visual reviews, repository administration, and more complex collaboration tasks.<\/p>\n\n\n\n
      \n\n\n\n
      18. GitHub CLI Best Practices<\/h1>\n\n\n\n
      For secure and reliable use, follow these guidelines:<\/p>\n\n\n\n
        \n
      1. Install GitHub CLI from official package repositories or trusted installers.<\/li>\n\n\n\n
      2. Keep your CLI version updated with security and compatibility fixes.<\/li>\n\n\n\n
      3. Use a secure authentication method and avoid exposing credentials.<\/li>\n\n\n\n
      4. Prefer short-lived, appropriately scoped credentials for automation.<\/li>\n\n\n\n
      5. Never commit access tokens or credentials to Git repositories.<\/li>\n\n\n\n
      6. Avoid passing sensitive tokens directly as command-line arguments.<\/li>\n\n\n\n
      7. Verify the active GitHub account and target repository before modifying resources.<\/li>\n\n\n\n
      8. Use GitHub CLI as a Git credential helper when appropriate for HTTPS workflows.<\/li>\n\n\n\n
      9. Review permissions before executing commands that modify repositories, issues, workflows, or releases.<\/li>\n\n\n\n
      10. Pin tested CLI versions in reproducible CI\/CD environments.<\/li>\n<\/ol>\n\n\n\n
        For automation, prefer securely supplied environment variables such as GH_TOKEN<\/code> rather than interactive gh auth login<\/code> sessions.<\/p>\n\n\n\n
        19. Conclusion<\/h2>\n\n\n\n
        GitHub CLI (gh<\/code>) is an essential command-line tool for developers, DevOps engineers, platform engineers, and anyone working extensively with GitHub.<\/p>\n\n\n\n
        It simplifies repository administration, pull request management, issue tracking, GitHub Actions monitoring, and automation.<\/p>\n\n\n\n
        Installation is straightforward across major operating systems:<\/p>\n\n\n\n