Potential fix for code scanning alert no. 3: Workflow does not contain permissions #147
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/codeharborhub/tutorial/security/code-scanning/3
In general, fix this by explicitly specifying the
permissionsfor the job or the workflow root so that theGITHUB_TOKENhas only the minimal scopes required. Here, thebuildjob only needs to read the repository contents (foractions/checkout) and upload a Pages artifact; that does not require repo write permissions. The safest minimal change is to addpermissions: contents: readto thebuildjob, mirroring the pattern already used in thedeployjob.Concretely, in
.github/workflows/deploy.yml, underjobs.buildand alongsidename:andruns-on:, insert apermissions:block withcontents: read. This keeps thedeployjob’s existing permissions (for Pages and OIDC) unchanged and does not alter any steps. No imports or additional methods are needed because this is purely workflow configuration.Suggested fixes powered by Copilot Autofix. Review carefully before merging.