GH CLI could not be found. GitHub CLI path does not persist.

[kroikie]

MacOS (Intel) Ventura 13.4 Codespaces plugin: 0.4.0.1233 Gateway: 2023.1.2 GH CLI: gh version 2.29.0 (2023-05-10) (installed via homebrew)

The codespaces plugin does not recognize the installed version of the the GH CLI. When manually setting the path to the GH CLI via the UI it does not persist. See screenshots below.

[thomas-sickert]

Hey @kroikie, sorry you're running into issues. I've flagged you into our new connection flow that doesn't require the gh CLI.

Please let me know if that works for you, and if you have any additional issues.

[kroikie]

Hi @thomas-sickert thanks for adding me to the new connection flow. How do I access that new flow?

[thomas-sickert]

No action needed on your side, it will just use a different connection provider under the hood. Are you still seeing issues?

[afcamps]

Hi @thomas-sickert , I have the same issue. Could you add me to the new connection flow please ? Thx

[eostrom-livefront]

Same problem – I set the CLI path but it isn't saved when I press OK. (Also, the Apply button remains disabled.)

[mathieumetral]

The plugin appears to be searching for the binary in the standard paths (like /usr/local/bin). If you install it in a local directory, it can't find it. Simply adding a symbolic link solves the problem (e.g., ln -s /path/to/your/gh /usr/local/bin/gh).

While this workaround is effective, it isn't an ideal solution. It would be great to fix the issue that prevents saving the binary's path.

[m-jung]

This is still true on

Windows 10 21H2 Codespaces plugin: 0.5.0.1214 Gateway: 2023.2.1 GH CLI: gh version 2.33.0 installed using the .exe from releases

[sdeering]

Run this on windows to get it working: winget install --id GitHub.cli

[m-jung]

Run this on windows to get it working: winget install --id GitHub.cli

This is not a matter of installing GitHub CLI but the GitHub Codespaces Provider only considering the default path ‪C:\Program Files\GitHub CLI\gh.exe on Windows when looking for gh.exe. It just ignores any other path specified.

[EzioMercer]

I have the same issue on Windows 10

[spanishkangaroo]

Hi @thomas-sickert , I have the same issue too. Could you add me to the new connection flow pleeeease? Thanks!