Potential fix for code scanning alert no. 2: Workflow does not contain permissions #140
+2
−0
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/zopefoundation/groktoolkit/security/code-scanning/2
To fix the problem, explicitly define the minimal required
GITHUB_TOKENpermissions for this workflow. Since the job only checks out code and commits changes to files in the repository, it needs repository contents write access, but does not require broader scopes such asactions,issues, orpull-requests.The best fix without changing existing functionality is to add a
permissionsblock at the workflow root (so it applies to all jobs) withcontents: write. Place this block after theon:section and beforeconcurrency:. This keeps the workflow’s behavior the same (it can still commit viaEndBug/add-and-commit@v9) while avoiding reliance on potentially broad repository defaults.No imports or external libraries are needed; this is a pure YAML configuration change inside
.github/workflows/sync.yml.Suggested fixes powered by Copilot Autofix. Review carefully before merging.