Rule: Automatic queue to merge (queue)

• #approved-reviews-by >= 1
• -closed [📌 queue requirement]
• #changes-requested-reviews-by = 0
• #review-requested = 0
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • -check-failure ~= ci-app-
    • -check-failure ~= ci-slackbot-
    • -check-failure ~= test-prod-node20 /
    • check-success ~= ci-app-launch-dev
    • check-success ~= ci-app-lint
    • check-success ~= ci-app-test

Rule: Automatic merge for Preparing next version (merge)

• -closed [📌 merge requirement]
• label = type/prepare-next-version
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• author = github-actions[bot]
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

---

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

---

Mergify commands and options

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