Repository navigation
ci: workflow permissions - #101
Merged
Merged
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
dermatz
marked this pull request as ready for review
January 21, 2026 12:59
dermatz
enabled auto-merge (squash)
January 21, 2026 12:59
dermatz
disabled auto-merge
January 21, 2026 17:24
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/OpenForgeProject/mageforge/security/code-scanning/4
In general, fix this by explicitly defining a
permissionsblock that limits theGITHUB_TOKENto the minimal scopes required. Place it either at the top level of the workflow (applies to all jobs) or under the specific job (functional-tests). Since this workflow has only one job and no steps need to write to the repository or PRs, the minimal safe configuration iscontents: read. If you’re confident the job does not need the token at all, you could setpermissions: {}to fully disable it, but to align with the CodeQL suggestion and common practice, usingcontents: readis appropriate.Concretely, edit
.github/workflows/functional-tests.ymland insert a top‑levelpermissions:block after thename:andon:sections and beforejobs:. The block should be:No additional methods, imports, or dependencies are required; this is a pure YAML configuration change to the GitHub Actions workflow.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.