Potential fix for code scanning alert no. 1: Workflow does not contain permissions #78
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/Solution-Desk/improve/security/code-scanning/1
In general, the fix is to explicitly declare a
permissionsblock so theGITHUB_TOKENhas only the minimal rights required. For this workflow, the job reads repository contents (viaactions/checkout) and runs local linting; it does not need any write capabilities or access to other scopes, socontents: readis sufficient.The best fix without changing existing functionality is to add a
permissionsblock at the job level for themarkdownjob. This keeps the change tightly scoped and ensures that only this job is affected. In.github/workflows/ci.yml, underjobs: markdown:, insert apermissions:key withcontents: read, indented to match the other job properties. No additional imports, methods, or definitions are needed because this is purely a configuration change in the GitHub Actions workflow YAML.Suggested fixes powered by Copilot Autofix. Review carefully before merging.