ci: add explicit GITHUB_TOKEN permissions to cron-vendor workflow - #334
Merged
Conversation
Co-authored-by: JarryShaw <15666417+JarryShaw@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix code scanning alert flagged in repository
ci: add explicit GITHUB_TOKEN permissions to cron-vendor workflow
Aug 13, 2026
JarryShaw
marked this pull request as ready for review
August 13, 2026 04:27
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.
CodeQL flagged the
cron-vendorworkflow (alert #1) for missing explicitpermissions, leaving theGITHUB_TOKENscope inherited from repo/org defaults — which may be broader than necessary.Changes
.github/workflows/cron-vendor.yml: Addedpermissions: contents: writeto thevendor-updatejob — the minimum required for committing and pushing vendor updates back to the repo.