Potential fix for code scanning alert no. 9: Workflow does not contain permissions#6
Merged
rossaddison merged 1 commit intomasterfrom Dec 20, 2025
Merged
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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/rossaddison/data-cycle/security/code-scanning/9
In general, the fix is to explicitly set a
permissionsblock either at the top (workflow-level, applying to all jobs by default) or within the specific job. Here we only have one job (tests), so either location works. To avoid changing behavior while still following least-privilege, the best starting point is the recommended minimal permissionscontents: read, which is sufficient foractions/checkout,actions/cache, and typical test/coverage workflows that do not write to the repository or manage PRs.The single best fix here is to add a workflow-level
permissionsblock right after thename: pgsqlline, applying to all jobs. That keeps functionality unchanged (the job will still be able to check out code and run tests) while reducing theGITHUB_TOKENto read-only contents. No additional methods, imports, or external definitions are required because this is just YAML configuration. Only.github/workflows/pgsql.ymlneeds to be edited, and only around the workflow header (after line 23).Suggested fixes powered by Copilot Autofix. Review carefully before merging.