Repository navigation
Fix: Let main always fast-forward to the generated release - #13
Merged
Merged
Conversation
main can hold commits develop lacks -- earlier release merges or a hotfix -- and then the release PR conflicted (python-multiplatform #10 was CONFLICTING). When main is not an ancestor of the source, the release commit now takes main as a second parent. Its tree is still the filtered develop tree, so main fast-forwards to release and the PR cannot conflict.
This was referenced Oct 2, 2026
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.
When main is not an ancestor of develop, the release commit takes main as a second parent; its tree stays the filtered develop tree, so the release PR can always fast-forward main. Tested in tools/release/test-sync-release.sh (49 passed, red before: 2 failures).
Closes #12