fix: Use release branches instead of direct push to main#39
Merged
Conversation
- Update versioning workflow to create release branches instead of pushing directly to protected main branch - Both release and next-snapshot jobs now create branches and prompt for PR creation - Update local scripts to follow the same pattern - Respects branch protection rules requiring PRs for main branch
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.
Problem
The versioning workflow was attempting to push directly to the protected
mainbranch, which is not allowed due to branch protection rules requiring changes through pull requests.Solution
.github/workflows/versioning.ymlto create release branches instead of pushing directly to mainreleaseandnext-snapshotjobs now:release/1.0.0orrelease/next-snapshot-1.0.1-SNAPSHOT)version-release.shandversion-next-snapshot.sh) to follow the same patternChanges
release/{version}branchrelease/next-snapshot-{version}branchThis respects branch protection rules and enables releases through pull requests for the main branch.