-
Notifications
You must be signed in to change notification settings - Fork 523
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
feat: add support for auto-backports #4990
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:)
I know that @axw approved of this, but for my understanding what is the reason for changing the backport tool? (afaik either can be automated) |
the tool used for local backport does not change, you can use whatever you want. To make the automated backport we proposed mergify over the GitHub action, for maintainability reasons, and features reasons (mergify offer more than auto-merge and auto-backport and all out of the box) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
docs issue is unrelated, merging |
Thanks @kuisathaverat |
@Mergifyio backport 7.x |
@Mergifyio backport 7.13 |
What does this PR do?
Enable backports with mergify for:
v7.13.0
v7.12.0
If any conflicts the PRs are created with the label
conflict
in addition a comment will be added with the actions to be done in order to fix the conflicts locally and push to the branch.Why is it important?
Mergify
provides different mechanism to interact with PRs and automate certain process.Some examples
Backports to 7.x -> elastic/apm-pipeline-library#995
Merges to master -> elastic/apm-pipeline-library#994
Issues
Actions
mergify
app in this project.