-
-
Notifications
You must be signed in to change notification settings - Fork 662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add workflow for backporting PRs #4912
Add workflow for backporting PRs #4912
Conversation
- Time saving for backporting bug fixes to stable branches - Apply to PRs before closing
@matmair LMK what you think of this. Making the backporting process easier will mean we can merge bug fixes in and quickly patch to the stable branch too |
How does this work with solving merge conflicts? |
I think if there are merge conflicts it will error out and we'd have to do it manually anyway |
Closing this out, as I have discoverd that the automatic release notes only work with PRs, not commits. So back-porting like this will not generate any release notes for bugfix releases. I will have to continue to manually cherry-pick each bug fix onto the stable branch and create a duplicate PR, in order to get the automated release notes |
@SchrodingersGat Why not letting this bot create the prs? |
@wolflu05 I misread the docs for this workflow and thought it would merge directly into the target branch, but reading the docs correctly I see it will actually create a PR. So,.let's give it a go. |
* Add workflow for backporting PRs - Time saving for backporting bug fixes to stable branches - Apply to PRs before closing * Cleanup .json file (cherry picked from commit 60f79a0)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Uses the backport-action github action.