‼️ Action Required ‼️

The configuration uses the deprecated merge_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
A brownout is planned on September 16th, 2024.
This option will be removed on October 21st, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: Automatic strict merge (queue)

• -closed [📌 queue requirement]
• #approved-reviews-by>=2
• #changes-requested-reviews-by=0
• #review-requested=0
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• base=master
• label!=do-not-merge
• label=ready-to-merge
• status-success="Validate"
• status-success=license/cla
• status-success=lint_test_build
• title~=^(build|ci|chore|docs|feat|fix|perf|refactor|revert|style|test)(\([^)]+\))?:\s.+$
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success = Summary
      • check-neutral = Summary
      • check-skipped = Summary
    • any of: [🛡 GitHub branch protection]
      • check-success = lint_test_build
      • check-neutral = lint_test_build
      • check-skipped = lint_test_build
    • any of: [🛡 GitHub branch protection]
      • check-success = license/cla
      • check-neutral = license/cla
      • check-skipped = license/cla
    • any of: [🛡 GitHub branch protection]
      • check-success = Validate
      • check-neutral = Validate
      • check-skipped = Validate

✅ Rule: Automatic head deletion (delete_head_branch)

• closed [📌 delete_head_branch requirement]

---

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

🚀  You can help us by becoming a sponsor!

---

1 not applicable rule

Rule: Automatic boxmoji merge (queue)

• -closed [📌 queue requirement]
• author=boxmoji
• files~=^i18n/
• title~=^(fix)\(i18n\)?:\supdate translations$
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• base=master
• status-success="Validate"
• status-success=license/cla
• status-success=lint_test_build
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success = Summary
      • check-neutral = Summary
      • check-skipped = Summary
    • any of: [🛡 GitHub branch protection]
      • check-success = lint_test_build
      • check-neutral = lint_test_build
      • check-skipped = lint_test_build
    • any of: [🛡 GitHub branch protection]
      • check-success = license/cla
      • check-neutral = license/cla
      • check-skipped = license/cla
    • any of: [🛡 GitHub branch protection]
      • check-success = Validate
      • check-neutral = Validate
      • check-skipped = Validate

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