Potential fix for code scanning alert no. 8: Workflow does not contain permissions - #34
Closed
SmetDenis wants to merge 1 commit into
Closed
Potential fix for code scanning alert no. 8: Workflow does not contain permissions#34SmetDenis wants to merge 1 commit into
SmetDenis wants to merge 1 commit into
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
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.
Potential fix for https://github.com/JBZoo/PHPUnit/security/code-scanning/8
The proper way to address this is to add a
permissionsblock at either the workflow or job level, specifying the least privilege required. Because there is no evidence that any step in any job needs write permissions, and most steps only require how to checkout code or upload artifacts, setting the minimal feasible permission (contents: read) at the workflow level makes sense. This will apply to all jobs (phpunit,linters,report) and can be overridden in any individual job if necessary in the future. To implement, add:immediately after the workflow
name:declaration (line 13). No further code, imports, or modifications are required, as this is a YAML/metadata configuration.Suggested fixes powered by Copilot Autofix. Review carefully before merging.