Open dark-light-cz opened 1 month ago
Hey @dark-light-cz, thanks for creating the issue and sorry you're having issues.
I can't see anything obviously wrong with what you are doing but I do have one hunch. Can you share how you installed gh
? Can you share the exact command you used when you ran gh auth status
e.g. was it ./gh auth status
? Basically I'd like to understand if gh
is on your PATH
, perhaps you can check with which gh
?
Hi I'm on debian11
gh is installed from oficial repository deb [arch=amd64 signed-by=/etc/apt/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main
using apt install gh
and copilot installed gh extension install github/gh-copilot
~$ apt-cache policy gh
gh:
Installed: 2.57.0
Candidate: 2.57.0
Version table:
*** 2.57.0 500
500 https://cli.github.com/packages stable/main amd64 Packages
100 /var/lib/dpkg/status
gh is used from /bin/
~$ which gh
/bin/gh
Alright, when I have a moment I'll see if I can reproduce this. Is there any other information you think might be useful for investigation? Did this ever work? Did it work when you weren't using the env var but maybe using gh auth login
?
It's the first time I'm trying to authenticate cli throuh env variable, so I don't know if it woked before.
It works well if I login using suggested gh auth login --web -h github.com
.
Thank you for your help.
Ok that's good to know. I haven't looked into how extensions work with environment variable auth before, so I'll have a look at that later. Thanks for the hints.
Issue description
When setting ENV variable for access token authentication for gh it works, but extension is not authenticated and keeps asking for login.
Versions
gh version 2.57.0 (2024-09-16) gh copilot github/gh-copilot v1.0.5
Relevant terminal output
ENV: setting:
gh auth check
ghcs call