Potential fix for code scanning alert no. 2: Workflow does not contain permissions #606
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/InnerSourceLearningPath/security/code-scanning/2
To fix the problem, set an explicit
permissionsblock in the workflow file, which restricts the default permissions of the GITHUB_TOKEN. As there is no evidence in the workflow file that it needs to modify code, open issues, or perform other write operations on the repository, the most restrictive appropriate permissions setting iscontents: read. This can be set at the root of the workflow (applies to all jobs), or specifically for thevalejob. The most typical approach (and as recommended by the error) is to add it at the top-level, just after the workflowname. No imports or code definitions are necessary for this change; just the addition of a top-level permissions block. Only .github/workflows/vale.yml must be modified.Suggested fixes powered by Copilot Autofix. Review carefully before merging.