Workflow does not contain permissions #222
Merged
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/nginx/nginx-supportpkg-for-k8s/security/code-scanning/49
The best way to fix this problem is to explicitly add a
permissionsblock at the top (workflow) level, beforejobs:, to restrict the GITHUB_TOKEN to minimal privileges. In most cases where the workflow does not need to write to the repository or PRs, settingpermissions: contents: readis considered the least-privilege minimal setting that still allows most basic Actions to function (checkout, etc.). This should be added right after the workflow's name and triggers, and before thejobs:key. No other content changes are needed.Suggested fixes powered by Copilot Autofix. Review carefully before merging.