fix: use PR-based flow in release script#8
Merged
Merged
Conversation
The release script previously pushed directly to main, which fails when GitHub Rulesets (GH013) enforce PR requirements. Now: - commit_repo creates a release/* branch instead of committing on main - push_repo pushes the branch, creates a PR via gh, squash-merges it, deletes the remote branch, and pulls main back to sync This works with 0-approval rulesets (self-merge) and keeps the release flow fully automated.
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.
Summary
commit_repocreates arelease/*branch instead of committing on mainpush_repopushes the branch, creates a PR, squash-merges, cleans up, and syncs mainTest plan
bash scripts/release.sh --dry-run --allow-dirty --no-clawdhub --no-homebrew --no-report