-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use gh
CLI to get OAuth token
#335
Comments
Note that as of https://github.com/cli/cli/releases/tag/v2.24.0 , the |
new user here, I'm confused by this as well, I did I've tried to configure manually token in ~/.config/hub by adding token from https://github.com/settings/tokens and update: storing the token in GH_TOKEN works |
I am trying to connect to our Github Enterprise server, and observe the same behaviour: Logged in fine when using Setting the token in |
TL;DR: For anyone struggling with this,
After |
As shared [in this comment](ejoffe#335 (comment)), gh cli has changed the default behavior of how github auth tokens are saved. This change makes spr no longer able to read github auth tokens and has caused myself and others confusion when instructions say to run `gh auth login` but still see spr not be able to find the token. This change updates the instructions to avoid this confusion. I do understand that suggesting to users to use insecure storage may not be ideal and a different solution may be preferred. Whatever solution it is, I believe it's better then today where users of spr receive these help docs, try them, and do not see success.
As shared [in this comment](#335 (comment)), gh cli has changed the default behavior of how github auth tokens are saved. This change makes spr no longer able to read github auth tokens and has caused myself and others confusion when instructions say to run `gh auth login` but still see spr not be able to find the token. This change updates the instructions to avoid this confusion. I do understand that suggesting to users to use insecure storage may not be ideal and a different solution may be preferred. Whatever solution it is, I believe it's better then today where users of spr receive these help docs, try them, and do not see success.
Hello everyone, First off, I'd like to say that this tool is fantastic—great work! I have a question regarding the selection options for scopes. Specifically, how many options should I select to appropriately define the access level for personal tokens? Thank you for your assistance! |
There are a few ways that the
gh
CLI represents a token, including via an environment variableGH_TOKEN
In my development environment
displays the the token.
However:
The text was updated successfully, but these errors were encountered: