‼️ 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: Automatically merge on CI success and review (queue)

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• approved-reviews-by=@oss-approvers
• base=master
• label=ready to merge
• status-success=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]
    • any of: [🛡 GitHub branch protection]
      • check-success = build
      • check-neutral = build
      • check-skipped = build

✅ Rule: Automatically merge on CI success and review (label)

• approved-reviews-by=@oss-approvers
• base=master
• label=ready to merge
• status-success=build

Rule: Automatically merge PRs from maintainers on CI success and review (queue)

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• author=@oss-approvers
• base=master
• label=ready to merge
• status-success=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]
    • any of: [🛡 GitHub branch protection]
      • check-success = build
      • check-neutral = build
      • check-skipped = build

✅ Rule: Automatically merge PRs from maintainers on CI success and review (label)

• author=@oss-approvers
• base=master
• label=ready to merge
• status-success=build

Rule: Automatically merge autobump PRs on CI success (queue)

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• author:spinnakerbot
• base~=^(master|release-)
• label~=autobump-*
• status-success=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]
    • any of: [🛡 GitHub branch protection]
      • check-success = build
      • check-neutral = build
      • check-skipped = build

✅ Rule: Automatically merge autobump PRs on CI success (label)

• author:spinnakerbot
• base~=^(master|release-)
• label~=autobump-*
• status-success=build

Rule: Request reviews for autobump PRs on CI failure (request_reviews)

• status-failure=build
• base=master
• base~=^(master|release-)
• label~=autobump-*

---

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

🚀  You can help us by becoming a sponsor!

---

2 not applicable rules

Rule: Automatically merge release branch changes on CI success and release manager review (queue)

• -closed [📌 queue requirement]
• base~=^release-
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• approved-reviews-by=@release-managers
• label=ready to merge
• status-success=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]
    • any of: [🛡 GitHub branch protection]
      • check-success = build
      • check-neutral = build
      • check-skipped = build

Rule: Automatically merge release branch changes on CI success and release manager review (label)

• base~=^release-
• approved-reviews-by=@release-managers
• label=ready to merge
• status-success=build

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