Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Mar 31, 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


This is an automatic backport of pull request #17347 done by [Mergify](https://mergify.com).

@mergify mergify bot added the backport label Mar 31, 2025
@mergify mergify bot assigned v1v Mar 31, 2025
@elastic-sonarqube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @v1v

@v1v v1v merged commit a10dbed into 8.x Mar 31, 2025
7 checks passed
@v1v v1v deleted the mergify/bp/8.x/pr-17347 branch March 31, 2025 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants