fix: grant actions:read to release CI gate - #263
Merged
Conversation
…query workflow runs The 'Require green CI on the tagged commit' step calls gh run list against the Actions API, but the job's permissions block only granted contents:read, so the default GITHUB_TOKEN got a 403 on GET /actions/workflows and the v0.1.0 release run failed before building anything.
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
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.
Summary
sign-artifacts("Require green CI on the tagged commit") withHTTP 403: Resource not accessible by integrationwhen callinggh run list --workflow CI.permissionsblock only grantedcontents: read, so the defaultGITHUB_TOKENhad no access toactions:*endpoints.actions: readto thesign-artifactsjob permissions so the CI-gate check can run.Test plan
v0.1.0and confirm thesign-artifactsjob's CI gate step succeeds and the release pipeline proceeds past it.