This is a tracking issue for rounding up everything related to Windows support in gh.

Issues

Packaging

• Support for Windows ARM #2545 Support Windows ARM
• Sign gh.exe binaries in addition to signing the MSI installer #2111 Sign gh.exe within MSI
• Provide non-admin mode from the Windows installer #1740 Non-admin mode for MSI
• Windows Installer - Back button not working on Ready To Install Page #1723 Broken back button in MSI
• Automatic WinGet pkg update #1262 Support WinGet
• MSI installer ignores selected target folder #703 MSI ignores target folder
• Add 32-bit Windows Support #2182 Support 32-bit in MSI

Bugs

• tab-completions for powershell don't work on the root command #1775 Tab completion problem in powershell
• Incorrect display of Chinese characters in Git Bash on Windows #1774 Incorrect display of chinese characters in gitbash
• Windows Installer - Back button not working on Ready To Install Page #1723 PAGER problem in Cygwin
• WSL 2 - gh repo view -w fails #3642 WSL2 browser error
• "Incorrect function" error in Windows Git Bash terminal #404 Error when using gitbash
• gh pr diff returns broken output when using delta pager on Windows #3703 Pager issues

Features

• Store gh config in %APPDATA% on windows #1944 Store gh config in %APPDATA%
• Repo garden for Windows #3223 Support repo garden
• Better detection of terminal environment on windows (ie PowerShell vs. GitBash vs. other)

Docs

• Clarify how to use the PowerShell completions #695 Better document completions in PowerShell
• Document minTTY (gitbash) workaround that is detailed in "Incorrect function" error in Windows Git Bash terminal #404

Notes

Part of what has made Windows support difficult is the variety of execution environments users might be using. We know we have many Windows users and can tell from within code when we're running on Windows; however, we have no insight right now into which of the many potential Windows environments someone is running gh in:

• Powershell
• Git Bash
• Cygwin
• cmd.exe
• WSL
• WSL2
• something else

Nor what terminal emulator might be in use:

• Windows Terminal
• mintty
• conhost.exe
• Hyper
• Alacritty
• something else

Depending on the combination from the above two lists there may be issues with tab completion, unicode rendering, and color palettes. Our confusion around what environments people are actually in has led to some paralysis in improving Windows support.

I propose:

• research spike on at least determining when we're running in PowerShell
• blessing some combinations of environments + terminal emulators as first class support targets
• write QA docs for the blessed environments + terminal emulators
• write public facing docs on setting up Windows for success with gh (Primarily targeted at installing and using a proper unicode-supporting font)