ci: Declare minimum permissions on semantic-commit workflow#51
Merged
maks-m-mongo-leaf merged 1 commit intoMay 26, 2026
Merged
Conversation
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
arpitjain099
requested review from
andmatei,
andreaangiolillo,
drinkbird,
lovisaberggren,
matt-condon,
saisundar and
wtrocki
Contributor
Author
|
Hi - just a gentle nudge for merge when you have a moment. @maks-m-mongo-leaf already approved. |
maks-m-mongo-leaf
changed the title
maks-m-mongo-leaf
changed the title
maks-m-mongo-leaf
changed the title
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.
Declares
permissions: contents: read, pull-requests: readat the workflow level on.github/workflows/semantic-commit.yaml.amannn/action-semantic-pull-requestreads the PR title via the pulls API to validate conventional-commit format and reports the result as the workflow's own check status. That needs read onpull-requestsand nothing else.Worth declaring explicitly even when the inherited default may already be reasonable: CVE-2025-30066 (the March 2025
tj-actions/changed-filescompromise) showed a tampered third-party action exfiltratingGITHUB_TOKENfrom workflow logs and the leaked token retaining whatever scope was issued at the workflow level. A per-workflow cap bounds the runtime authority of every action that runs inside it irrespective of repo or org default, gives drift protection if that default ever widens, and registers with OpenSSF Scorecard's Token-Permissions check.YAML validated locally with
yaml.safe_load.