Declare explicit GITHUB_TOKEN permissions in workflows - #1
Merged
Conversation
Sets least-privilege permissions on each workflow so they keep working once the org default token permission is switched to read-only.
greg0x
approved these changes
Aug 30, 2026
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
2 participants
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.
Adds a top-level
permissions:block so each workflow declares the GITHUB_TOKEN scopes it needs. This is part of the org-wide switch to a read-only default token permission: workflows that declare their own scopes keep working unchanged after the switch.Workflows: format.yml (
contents: write— its jobs commit and push formatting fixes), validate.yml (contents: read)No behaviour change.