-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
ci(backport): remove former approach #17347
Conversation
|
@Mergifyio rebase |
✅ Branch has been successfully rebased |
547b378
to
63d88ad
Compare
💔 Build Failed
Failed CI Steps
History
cc @v1v |
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.
LGTM
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.
LGTM!
From my side, I have been facing any issues with Mergify so far.
For some special cases, I had called it and run with comments, working as expected.
And CI failures seem not related to this PR.
(cherry picked from commit 26af21d)
(cherry picked from commit 26af21d)
(cherry picked from commit 26af21d) Co-authored-by: Victor Martinez <[email protected]>
(cherry picked from commit 26af21d) Co-authored-by: Victor Martinez <[email protected]>
Release notes
[rn:skip]
What does this PR do?
Remove the former approach for backporting.
Why is it important/What is the impact to the user?
Mergify was enabled, see #16933
Checklist
Author's Checklist
How to test this PR locally
Related issues
Part of #16933
Use cases
Screenshots
Logs