feat(release): Ruleset-aware push with PR creation fallback - #125
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.
Description
I've improved the
releasecommand's resilience when pushing changes to a remote repository protected by GitHub rulesets or branch protection rules.Specifically, when a direct
git push(for commits or tags) is rejected by a ruleset, the system now detects this specific error (ErrPushRejectedByRuleset). For thereleasecommand's final push, if the direct push fails due to a ruleset, it will now automatically create a new branch (matecommit/release-vX.Y.Z), push the release changes to this new branch, and then open a Pull Request into the original base branch. This allows the release process to continue through a PR merge.Additionally, I've updated the UI to display the specific
stderroutput from Git when a ruleset rejection occurs, providing clearer feedback to the user.Fixes #
Type of Change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist
Test Plan & Evidence
Suggested Manual Verification
go test ./...and ensure all tests pass