ci: scope down GitHub Token permissions#270
Closed
AdnaneKhan wants to merge 2 commits into
Closed
Conversation
|
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
1 participant
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.
Scope Down GitHub Token Permissions
This PR updates GitHub Actions workflows to use minimal required permissions instead of the default elevated permissions.
Why This Matters
Following the principle of least privilege, workflows should only have the specific permissions they need to function.
Changes
This PR adds explicit
permissions:blocks to workflows that currently rely on default permissions, scoping them down to only what's required for their operations.Please review the changes to ensure the specified permissions match your workflow requirements.