Potential fix for code scanning alert no. 262: Workflow does not contain permissions - #55
Merged
Conversation
…ain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
joel-rieke
marked this pull request as ready for review
January 28, 2026 18:26
meghan-bailey
approved these changes
Jan 28, 2026
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
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/trimble-oss/go-mysql-server/security/code-scanning/262
To fix the problem, we should add an explicit
permissionsblock to the workflow. The best practice is to set the minimal permissions required for the workflow to function. Since the workflow has three jobs:format: usesEndBug/add-and-commit@v9.1.1to commit changes, so it needscontents: write.verifyandalt-verify: only need to read repository contents.We can set a default
permissionsblock at the workflow level withcontents: read, and override it for theformatjob withcontents: write. This ensures that only the job that needs write access gets it, and all others are restricted to read-only.The changes should be made at the top of the workflow file (after the
name:and beforeon:), and within theformatjob definition.Suggested fixes powered by Copilot Autofix. Review carefully before merging.