Rule: enqueue on label (queue)

• base=dev
• label=merge-queue
• -draft [📌 queue requirement]
• -mergify-configuration-changed [📌 queue -> allow_merging_configuration_change setting requirement]
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue dev]
    • #approved-reviews-by>=1 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success=build-debug-clang-amd64
      • check-neutral=build-debug-clang-amd64
      • check-skipped=build-debug-clang-amd64
    • any of: [🛡 GitHub branch protection]
      • check-success=build-release-clang-amd64
      • check-neutral=build-release-clang-amd64
      • check-skipped=build-release-clang-amd64
    • any of: [🛡 GitHub branch protection]
      • check-success=ducktape-build-debug-clang-amd64
      • check-neutral=ducktape-build-debug-clang-amd64
      • check-skipped=ducktape-build-debug-clang-amd64
    • any of: [🛡 GitHub branch protection]
      • check-success=ducktape-build-release-clang-amd64
      • check-neutral=ducktape-build-release-clang-amd64
      • check-skipped=ducktape-build-release-clang-amd64

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