Potential fix for code scanning alert no. 16: Workflow does not contain permissions#313
Draft
Potential fix for code scanning alert no. 16: Workflow does not contain permissions#313
Conversation
…in permissions 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/rtCamp/login-with-google/security/code-scanning/16
In general, to fix this problem, add an explicit
permissions:block either at the top level of the workflow (to apply to all jobs) or within thereleasejob to restrict the defaultGITHUB_TOKENpermissions to only what’s required. Since this workflow only has a single job, addingpermissions:underjobs.releaseis sufficient and makes the job’s requirements explicit.For this specific workflow, the steps suggest the following needs:
actions/checkoutand read access to repository contents:contents: readsoftprops/action-gh-releasecreates or updates a GitHub Release and uploads assets, which requires write access to repository contents/releases:contents: writeNo other GitHub write scopes (issues, pull-requests, etc.) are obviously required. Therefore, the best minimal change is to add a
permissions:block underjobs.releasethat grantscontents: write. This automatically includes read, satisfying bothcheckoutand the release action. The change should be inserted directly underruns-on: ubuntu-latest(line 8) in.github/workflows/release_plugin_on_tag.yml. No imports or additional definitions are needed since this is purely a YAML configuration change.Suggested fixes powered by Copilot Autofix. Review carefully before merging.