[Fix] Scope GitHub Actions write permissions to the build-test job (SonarCloud S8233)#110
Merged
Merged
Conversation
Contributor
|
|
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.



What
Resolves the 2 open SonarCloud MAJOR vulnerabilities (rule
githubactions:S8233, "Move this write permission from workflow level to job level") on.github/workflows/CodeQuality.yml.Why
checks: writeandpull-requests: writewere declared at the workflow level, so every job in the workflow received them. Only thebuild-testjob actually uses them:checks: write→dorny/test-reporterpull-requests: write→ the stickycode-coveragecomment (marocchino/sticky-pull-request-comment) and the coverage-summary stepsThe
build(SonarCloud) andvalidate-tooljobs only need read access — SonarCloud PR decoration is done viaSONAR_TOKEN, not the GitHub token.Change
permissionsreduced to the read-only defaultcontents: read.permissionsblock onbuild-testonly (a job-level block overrides the workflow default, socontents: readis repeated for checkout):buildandvalidate-toolinherit the read-only default (all they need).No CI behaviour changes: the test reporter check run and the sticky coverage comment still work because the scopes now live on the job that uses them.
Verification
build-testhas the three scopes,build/validate-toolhave none.build/validate-toolsucceed read-only.githubactions:S8233count should drop from 2 → 0.