fix(ci): workflow does not contain permissions #47
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/offlegacy/git-intent/security/code-scanning/8
In general, this type of problem is fixed by explicitly declaring a
permissionsblock for the workflow or for each job, restricting theGITHUB_TOKENto only the scopes actually needed. For a code‑quality workflow that only checks out code and runs local analysis,contents: readis typically sufficient.For this specific workflow in
.github/workflows/code-quality.yml, the simplest, non‑breaking fix is to add a root‑levelpermissionsblock (applies to all jobs) withcontents: read. The job only needs to read the repository contents (viaactions/checkout@v4) and does not require any write access or other scopes. No other permissions (likepull-requestsorissues) are needed based on the current steps.You should edit
.github/workflows/code-quality.ymlto insert:between the
name:andon:keys (or alternatively betweenon:andjobs:; root level is what matters). No imports or additional methods are needed, since this is a YAML configuration change only.Suggested fixes powered by Copilot Autofix. Review carefully before merging.