Rule: put PR in draft if conflicts (edit)

• author = mergify[bot]
• label = conflicts

Rule: Automate backport pull request 5.2 (backport)

• base=master
• label=backport/5.2
• merged [📌 backport requirement]

Rule: Automate backport pull request 5.4 (backport)

• base=master
• label=backport/5.4
• merged [📌 backport requirement]

Rule: Automate backport pull request 6.0 (backport)

• base=master
• label=backport/6.0
• merged [📌 backport requirement]

Rule: Automate backport pull request 2023.1 (backport)

• base=master
• label=backport/2023.1
• merged [📌 backport requirement]

Rule: Automate backport pull request 2024.1 (backport)

• base=master
• label=backport/2024.1
• merged [📌 backport requirement]

Rule: Automate backport pull request 2024.2 (backport)

• base=master
• label=backport/2024.2
• merged [📌 backport requirement]

Rule: Automate backport pull request perf-v14 (backport)

• base=master
• label=backport/perf-v14
• merged [📌 backport requirement]

Rule: Automate backport pull request perf-v15 (backport)

• base=master
• label=backport/perf-v15
• merged [📌 backport requirement]

Rule: Automate backport pull request manager-3.2 (backport)

• base=master
• label=backport/manager-3.2
• merged [📌 backport requirement]

Rule: Automate backport pull request manager-3.3 (backport)

• base=master
• label=backport/manager-3.3
• merged [📌 backport requirement]

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com