Potential fix for code scanning alert no. 3: Workflow does not contain permissions #828
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/projectcaluma/ember-emeis/security/code-scanning/3
In general, the fix is to explicitly set
permissionsfor the workflow or for each job to ensure theGITHUB_TOKENhas only the minimal required privileges. Since these jobs only need to read the repository contents (foractions/checkoutand to run code), we can setcontents: read. Doing this at the workflow root is simplest and applies to all jobs that lack their ownpermissionsblock, matching the CodeQL suggestion and preserving existing behavior.The best change here is to add a single
permissions:block at the top level of.github/workflows/test.yml, just below theon:section (or just after it) so it clearly applies to all jobs. We’ll set:No job-specific modifications or additional imports are needed. Functionality remains unchanged, but the
GITHUB_TOKENwill now be restricted to read-only repository contents for all jobs in this workflow.Suggested fixes powered by Copilot Autofix. Review carefully before merging.