Potential fix for code scanning alert no. 11: Workflow does not contain permissions #878
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/InnerSourceCommons/InnerSourcePatterns/security/code-scanning/11
To fix the problem, you should explicitly declare a
permissionsblock at the workflow (top) or job (vale job) level. This block should enumerate only the minimum permissions needed for the workflow's actions. In this specific case, the job only checks out code and runs Vale analysis. No write access or additional scopes are needed;contents: readwill suffice.The most straightforward method is to add
permissions: contents: readnear the top (right under thename) so it applies to all jobs in the workflow. Alternatively, you can add it under thevalejob for just that job—but given there is only one job, placing it under the workflow header is cleaner.What to change:
Modify
.github/workflows/vale.ymlto insert:just after the
name: Spelling & Stylesline and before theon:block.No additional imports, methods, or definitions are required since this is just a configuration file change.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.