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

Create mergify config for 8.x backports #40670

Merged
merged 1 commit into from
Sep 1, 2024
Merged

Conversation

pierrehilbert
Copy link
Collaborator

Proposed commit message

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
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@pierrehilbert pierrehilbert requested a review from a team as a code owner September 1, 2024 14:29
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 1, 2024
@botelastic
Copy link

botelastic bot commented Sep 1, 2024

This pull request doesn't have a Team:<team> label.

Copy link
Contributor

mergify bot commented Sep 1, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @pierrehilbert? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@pierrehilbert pierrehilbert merged commit 6884f37 into main Sep 1, 2024
10 checks passed
@pierrehilbert pierrehilbert deleted the pierrehilbert-patch-3 branch September 1, 2024 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant