Potential fix for code scanning alert no. 1: Workflow does not contain permissions#2361
Merged
Potential fix for code scanning alert no. 1: Workflow does not contain permissions#2361
Conversation
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
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/react-native-community/directory/security/code-scanning/1
In general, the fix is to explicitly define a
permissionsblock that grants the minimal required scopes toGITHUB_TOKEN. For this workflow, the job only needs read access to the repository contents foractions/checkout@v6; all deployment credentials come fromsecrets, so no additional write permissions are required.The best minimal fix without changing existing functionality is to add a
permissionsblock withcontents: read. We can add it either at the root of the workflow (applying to all jobs) or at thebuildjob level. To keep the change tightly scoped to the CodeQL-highlighted job, we’ll add it underjobs.build, aligned withruns-on. Concretely, in.github/workflows/code-deploy-producition-quick.yml, between lines 10 and 11 (betweenbuild:andruns-on:), insert:No imports or additional definitions are needed, since this is a YAML configuration change only.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.