Grant contents:write to Cut Release so it can push the branch - #8
Merged
Merged
Conversation
The default GITHUB_TOKEN is read-only, so cut_release failed at push with "Permission denied to github-actions[bot]" (403). Add contents:write, matching the publish workflow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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
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.
cut_releasegot through commit but failed atpush_to_git_remote:The
cut-release.ymlworkflow didn't declarepermissions, so theGITHUB_TOKENdefaulted to read-only and couldn't push the newrelease/*branch. Addspermissions: contents: write(same aspublish.yml).🤖 Generated with Claude Code