ci: set workflow permissions#1316
Open
Belco90 wants to merge 1 commit into
Open
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Mario Beltrán <me@belco.dev>
Belco90
changed the title
MichaelDeBoey
approved these changes
May 13, 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
2 participants
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/testing-library/eslint-plugin-testing-library/security/code-scanning/4
In general, fix this by adding an explicit
permissionsblock either at the workflow root (to cover all jobs) or on the specific job, granting only the minimal required scopes. For a workflow that only reads workflow/job state and does not interact with repository contents or PRs, it is safe to setpermissions: contents: readat the workflow level; this is the common minimal baseline and aligns with GitHub’s recommendation for read-only defaults.The best targeted fix here is to define
permissionsat the workflow root, just belowname: CI, so that bothverificationsandrequired-checksjobs inherit it unless they define their own. Given the information in the snippet, the minimal sane configuration is:This explicitly restricts
GITHUB_TOKENto read-only repository contents, which is sufficient for typical CI and avoids unexpected write capabilities. No new imports, actions, or logic changes are needed; only the YAML workflow header is updated. Concretely, in.github/workflows/ci.yml, insert apermissionsblock after line 1 and beforeon:at line 3.Suggested fixes powered by Copilot Autofix. Review carefully before merging.