Grant the cut token workflow permission and make the cut resumable - #3
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
1 participant
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.
Second rehearsal finding: pushes touching
.github/workflows/*require the app to hold the Workflows permission, so the cut'sRELEASE_VERSIONedit onmain.ymlwas rejected (GH013 … without \workflows` permission). The contents token now requestspermission-workflows: write(requires the Workflows permission to be added to the app installation). The cut also becomes resumable: when the maintenance branch already exists butmainis not yet in pre-release mode — exactly the state a mid-cut failure leaves behind — it resumes from themain` step instead of failing.