Potential fix for code scanning alert no. 1: Workflow does not contain permissions #8
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/dorukozerr/kisuke.vim/security/code-scanning/1
To fix the problem, add the
permissionskey to the workflow or the specific job to explicitly restrict the GITHUB_TOKEN permissions to the minimum required. For a workflow that simply runs code quality checks (linting and formatting), only read access to repository contents is needed. The recommended fix is to addpermissions: contents: readimmediately below the workflowname:at the top level, making it apply universally to all jobs in this workflow. Alternatively, you could add it under each job, but the top-level placement is cleaner and follows the recommendation. No new imports or definitions are needed; only a single line should be added near the top of .github/workflows/code-quality.yml, right beneathname: Code Quality Checks.Suggested fixes powered by Copilot Autofix. Review carefully before merging.