Release fork PRs via an auto-merging bump PR - #285
Merged
Merged
Conversation
The ruleset forbids direct pushes to main, so the previous approach of pushing the fork version bump straight to main from Publish failed (GH013: changes must be made through a pull request). Instead, when a fork PR merges, open-release-bump-pr opens an in-repo 'release bump' PR carrying the same release label and the fork PR's notes. It rides the existing same-repo flow (validate + sync) and auto-merges; Publish then tags it. The v*.*.* tag — and the APK build that keys off it — therefore happens only after the bump PR merges, i.e. on the merged fork code at its new version. Same-repo PRs are unchanged.
mister-teddy
added
the
release:docs
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.
No description provided.