ci: adopt shared back-merge workflow - #25
Merged
Merged
Conversation
1 task
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.
What
Adds
.github/workflows/backmerge.yaml, which fast-forwardsdeveloptomasteronce a release PR merges. Delegates to the shared reusableworkflow at
qtmleap/actions.Why
developandmasterdrift apart after every release until someoneback-merges by hand. This closes that gap automatically.
workflow_dispatchis kept for manual recovery — it warns and no-ops when a fast-forward is
not possible, so it is safe to run at any time.
Version
No bump. CI-only change;
pyproject.tomlstays at0.3.0.Test plan
pull_request: closedagainstmasterwith
merged == true, or manual dispatch🤖 Generated with Claude Code