‼️ 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 August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

‼️ Action Required ‼️

The configuration uses the deprecated update_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 August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: automatic squash-merge for master when CI passes and approved (queue)

• #approved-reviews-by>=1
• -draft [📌 queue requirement]
• all of:
  • check-success=SonarCloud Code Analysis
  • check-success=all-tests
  • check-success=docker
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by>=1 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success=all-tests
      • check-neutral=all-tests
      • check-skipped=all-tests
    • any of: [🛡 GitHub branch protection]
      • check-success=docker
      • check-neutral=docker
      • check-skipped=docker
• base=master
• any of: [📌 queue -> 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!

---

1 not applicable rule

Rule: automatic merge for stable when CI passes and approved (queue)

• #approved-reviews-by>=1
• -draft [📌 queue requirement]
• base=stable
• all of:
  • check-success=SonarCloud Code Analysis
  • check-success=all-tests
  • check-success=docker
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by>=1 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success=all-tests
      • check-neutral=all-tests
      • check-skipped=all-tests
    • any of: [🛡 GitHub branch protection]
      • check-success=docker
      • check-neutral=docker
      • check-skipped=docker
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed

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