Skip to content
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

Merged
merged 1 commit into from
Mar 31, 2025

Conversation

v1v
Copy link
Member

@v1v v1v commented Mar 18, 2025

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

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files (and/or docker env variables)
  • I have added tests that prove my fix is effective or that my feature works

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Part of #16933

Use cases

Screenshots

Logs

@v1v v1v added backport-8.x Automated backport to the 8.x branch with mergify backport-active-9 Automated backport with mergify to all the active 9.[0-9]+ branches labels Mar 18, 2025
@v1v v1v requested a review from pazone March 18, 2025 13:44
@v1v v1v self-assigned this Mar 18, 2025
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@v1v
Copy link
Member Author

v1v commented Mar 26, 2025

@Mergifyio rebase

Copy link

mergify bot commented Mar 26, 2025

rebase

✅ Branch has been successfully rebased

@v1v v1v force-pushed the feature/remove-former-backport-approach branch from 547b378 to 63d88ad Compare March 26, 2025 12:33
@v1v v1v requested review from robbavey and mashhurs March 28, 2025 07:28
Copy link
Member

@robbavey robbavey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@mashhurs mashhurs left a 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.

@v1v v1v merged commit 26af21d into elastic:main Mar 31, 2025
6 of 7 checks passed
mergify bot pushed a commit that referenced this pull request Mar 31, 2025
mergify bot pushed a commit that referenced this pull request Mar 31, 2025
v1v added a commit that referenced this pull request Mar 31, 2025
(cherry picked from commit 26af21d)

Co-authored-by: Victor Martinez <[email protected]>
v1v added a commit that referenced this pull request Mar 31, 2025
(cherry picked from commit 26af21d)

Co-authored-by: Victor Martinez <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify backport-active-9 Automated backport with mergify to all the active 9.[0-9]+ branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants