Repository navigation
PAT scopes - unclear correspondence between short names and long names #10131
Description
When using PAT to perform gh auth login, gh says that "The minimum required scopes are 'repo', 'read:org', 'admin:public_key'.". It is not clear which options these short names correspond to in the list of permissions shown when generating a PAT. See attached image.
Because the correspondence is not clear, it's furthermore not clear how to create a PAT with the minimum scopes - instead, I have to use all scopes.
Activity
jtmcg commentedon Dec 23, 2024
Hey @erikv85, it looks like you're trying to use a Fine-grained token. As far as I know, the CLI doesn't support Fine-grained tokens. You should use a "classic" token instead. The permission names 'repo', 'read:org', and 'admin:public_key' map 1:1 with permissions there:
Perhaps an indication that the token required for auth is a "classic" token in the token prompt would have been helpful?
erikv85 commentedon Dec 30, 2024
Hi @jtmcg , thanks for the quick reply. Yes, I think an indication of some sort that a classic token must be used could be helpful. I'm not sure much else could be done to help users, quite frankly.
jtmcg commentedon Jan 2, 2025
Acceptance Criteria
gh auth loginmentions that GitHub classic tokens are used for auth withgh