-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Pre-select scopes in new token link #12
Labels
documentation
Improvements or additions to documentation
Comments
That's a fantastic idea! Mind opening a pull request with that change? ❤️ |
FiXato
added a commit
to FiXato/gitty
that referenced
this issue
Sep 7, 2021
As per issue muesli#12 this change pre-fills the minimum required scopes for the personal access token. I've also included a default description of 'gitty' for the 'note' field. Since the link now points directly to the 'new token' form, I've also changed the clickable part of the sentence from 'profile settings' to 'create a new token' to better reflect the action of the link.
Done :) |
Just a thought - when gitty does not find either GITHUB_TOKEN or GITTY_TOKEN - would it be possible and considered practical to open the browser at that location (maybe after asking for permission to do so)? |
muesli
pushed a commit
that referenced
this issue
Sep 7, 2021
As per issue #12 this change pre-fills the minimum required scopes for the personal access token. I've also included a default description of 'gitty' for the 'note' field. Since the link now points directly to the 'new token' form, I've also changed the clickable part of the sentence from 'profile settings' to 'create a new token' to better reflect the action of the link.
@elbosso I agree, we should ideally do that. Mind opening a separate issue for that feature? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Might it be an idea to pre-select the required scopes in the "new personal access token" link in the README by adding the relevant scopes as comma-separated values for the 'scopes' parameter, e.g.: https://github.com/settings/tokens/new?scopes=repo:status,public_repo,read:user,read:org
The text was updated successfully, but these errors were encountered: