CLOUD-929 Potential fix for code scanning alert no. 13: Workflow does not contain permissions#2268
Merged
CLOUD-929 Potential fix for code scanning alert no. 13: Workflow does not contain permissions#2268
Conversation
…in permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Collaborator
commit: a54c432 |
egegunes
approved these changes
Mar 9, 2026
gkech
approved these changes
Mar 9, 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/percona/percona-server-mongodb-operator/security/code-scanning/13
In general, the fix is to add an explicit
permissions:block limiting theGITHUB_TOKENto the minimal scopes required. Since this workflow primarily checks code, runs linters/formatters, and performsgit diffchecks, read access to repository contents is sufficient; the actions that post comments or checks are using a separategithub_tokensecret, so they do not need additionalGITHUB_TOKENprivileges. The best minimal fix, without changing existing functionality, is to add a top-levelpermissions:section right under the workflowname:(beforeon:), settingcontents: read. This will apply to all jobs (golangci-lint,gofmt,goimports-reviser,shfmt,shellcheck,misspell,alex,manifests) unless overridden per job. No imports or extra methods are needed; this is a pure YAML configuration change in.github/workflows/reviewdog.yml.Concretely: edit
.github/workflows/reviewdog.ymlaround the top of the file. After line 1 (name: reviewdog), insert:leaving the rest of the file unchanged. This documents the intended permissions and ensures a restricted token even if repository/org defaults change later.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.