docs(graphql): order token scopes by form order #16715
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why:
The order of the scopes on the Forming calls with GraphQL page is not the same as the order of the form to create a personal access token.
It might also be useful to remove
repo
from the list - as it implies checking all the nested repo boxes.A second useful clarification here might be documenting the parent scope as well as the child scope - to allow for easy scanning.
Scope order on Forming calls with GraphQL page
https://docs.github.com/en/graphql/guides/forming-calls-with-graphql
Scope order on create a personal access token page
What's being changed:
Check off the following:
Writer impact (This section is for GitHub staff members only):