Repository navigation
fix(ci): retain Actions and pull request read permissions - #30
Merged
Merged
Conversation
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.
Change
Retain
contents: read,actions: read, andpull-requests: readin the reusable CI workflow so callermake checkcommands can read Actions evidence and pull request provenance withGITHUB_TOKEN.The callee previously reduced the token to
contents: readeven when a caller requested the other reads. No callee job overrides this permission map. Update this repository's self-CI caller, the caller template, and the documented examples to grant the same reads explicitly; GitHub reusable workflows cannot raise caller permissions.Verification
make checkpassed: actionlint, shellcheck, and all 36 Python tests.git diff --checkpassed.Rollout boundary
This PR changes source only. The existing
v2tag is unchanged. The D36 G0 GitOps caller will consume the exact merged commit after its caller grants these reads; the controller coordinates that pin and any later estate-widev2rollout. No other repositories, settings, grants, releases, or deployments are changed here.