Potential fix for code scanning alert no. 1: Workflow does not contain permissions #34
+3
−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/davep/complexitty/security/code-scanning/1
In general, the fix is to add an explicit
permissions:block that grants only the minimal required scopes for this workflow. Since this workflow just checks out the repo and runs local quality checks, it only needs to read repository contents. The recommended minimal starting point from CodeQL iscontents: read, which is sufficient foractions/checkoutand does not grant any write access.The best targeted fix without changing existing functionality is to add a
permissions:block at the workflow root (alongsidename:andon:). That will apply to all jobs (currently onlyquality-checks) that don’t declare their own permissions. Concretely, in.github/workflows/code-checks.yaml, between the existingname: Code quality checks(line 1) and theon:block (line 3), insert:No imports or additional methods are needed because this is a YAML configuration change only.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.