Potential fix for code scanning alert no. 3: Workflow does not contain permissions #832
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/openfoodfacts/openfoodfacts-web/security/code-scanning/3
To fix the problem, we need to set a
permissionsblock at the workflow or job level. Since theupdate-assetsjob is the only job, we can add it at the root of the workflow YAML. However, this workflow uses thepeter-evans/create-pull-requestaction, which requirescontents: write(to push new commits and branches) and optionallypull-requests: write(to open a PR). At a minimum, we should grantcontents: writeat the workflow level, and can optionally addpull-requests: writefor best compatibility. The change goes at the root, immediately after thename:field and before theon:block.permissions:block with values:pull-requests: writeif you want to follow the full CodeQL guidance and future-proof for actions that require explicit permission to open pull requests.Suggested fixes powered by Copilot Autofix. Review carefully before merging.