‼️ 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: Auto merge (feature branch) (queue)

• #approved-reviews-by>=1
• check-success=Checks (clippy)
• check-success=Checks (parachain)
• check-success=Checks (standalone)
• check-success=Coverage
• check-success=Format
• check-success=Fuzz
• check-success=Quick check benchmarks
• check-success=Test parachain build
• check-success=Test standalone build
• label=s:accepted
• #changes-requested-reviews-by=0
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• base!=main
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🔀 queue conditions]
  • all of [📌 queue conditions of queue default]

Rule: Auto merge (feature branch) (label)

• #approved-reviews-by>=1
• check-success=Checks (clippy)
• check-success=Checks (parachain)
• check-success=Checks (standalone)
• check-success=Coverage
• check-success=Format
• check-success=Fuzz
• check-success=Quick check benchmarks
• check-success=Test parachain build
• check-success=Test standalone build
• label=s:accepted
• #changes-requested-reviews-by=0
• base!=main

Rule: ask to resolve conflict (comment, label)

• conflict

Rule: Set in-progress label after changes are pushed (label)

• commits[-1].date_committer>=0 days 00:01 ago
• commits[-1].author!=mergify[bot]

Rule: Trigger CI after Mergify merged the base branch (fix merge queue) (label)

• commits[-1].author=mergify[bot]
• commits[-1].date_committer>=0 days 00:01 ago
• queue-position=0

Rule: Remove CI trigger label (label)

• commits[-1].author=mergify[bot]
• label=s:review-needed
• queue-position=0

---

💖  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: Auto merge (main) (queue)

• #approved-reviews-by>=1
• base=main
• check-success=Checks (clippy)
• check-success=Checks (parachain)
• check-success=Checks (standalone)
• check-success=Copyright Notices
• check-success=Coverage
• check-success=Format
• check-success=Fuzz
• check-success=Quick check benchmarks
• check-success=Test parachain build
• check-success=Test standalone build
• label=s:accepted
• #changes-requested-reviews-by=0
• -closed [📌 queue requirement]
• -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]

Rule: Auto merge (main) (label)

• #approved-reviews-by>=1
• base=main
• check-success=Checks (clippy)
• check-success=Checks (parachain)
• check-success=Checks (standalone)
• check-success=Copyright Notices
• check-success=Coverage
• check-success=Format
• check-success=Fuzz
• check-success=Quick check benchmarks
• check-success=Test parachain build
• check-success=Test standalone build
• label=s:accepted
• #changes-requested-reviews-by=0

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