Conversation
gzapf-cf
force-pushed
the
api-token-template-permission-group-ids
branch
from
September 21, 2026 13:37
45fef76 to
c5e0c70
Compare
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Updates the API token template URLs page to document permission group IDs as a
keyvalue and to correct the resolution behavior, which differs between account token URLs and user token URLs.Account token deep-links resolve a
permissionGroupKeysentry by short key or by permission group ID, and surface a notice for unresolved or malformed input instead of dropping it silently. User token URLs keep the narrower contract (short keys only, exactname+typematch,editnotwrite, silent drop on mismatch). The previous page described a single shared behavior, which is no longer accurate.Documentation checklist