⚠️ The pull request has been merged by @jeanplevesque

‼️ 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.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: automatic strict merge when CI passes, has 2 reviews, no requests for change and is labeled 'ready-to-merge' unless labelled 'do-not-merge/breaking-change' or 'do-not-merge/work-in-progress' (queue)

• -closed [📌 queue requirement]
• label=ready-to-merge
• #approved-reviews-by>=2
• #changes-requested-reviews-by=0
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• base=main
• label!=do-not-merge/breaking-change
• label!=do-not-merge/work-in-progress
• status-success=nventive.FlutterApplicationTemplate
• 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]
    • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success = nventive.FlutterApplicationTemplate
      • check-neutral = nventive.FlutterApplicationTemplate
      • check-skipped = nventive.FlutterApplicationTemplate
    • any of: [🛡 GitHub branch protection]
      • check-success = validate-commits
      • check-neutral = validate-commits
      • check-skipped = validate-commits

---

💖  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 merge for allcontributors pull requests (merge)

• -closed [📌 merge requirement]
• author=allcontributors[bot]
• #approved-reviews-by >= 2 [🛡 GitHub branch protection]
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
• #commits-behind = 0 [🛡 GitHub branch protection]
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🛡 GitHub branch protection]
  • check-success = nventive.FlutterApplicationTemplate
  • check-neutral = nventive.FlutterApplicationTemplate
  • check-skipped = nventive.FlutterApplicationTemplate
• any of: [🛡 GitHub branch protection]
  • check-success = validate-commits
  • check-neutral = validate-commits
  • check-skipped = validate-commits

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