‼️ 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 merge on approval (main) (queue)

• all of:
  • #approved-reviews-by>=1
  • check-success=ci/circleci: executor-tests
  • check-success=ci/circleci: plugins-tests
  • #changes-requested-reviews-by=0
  • #review-threads-unresolved=0
  • base=main
  • check-success=ci/circleci: contracts-tests
  • check-success=ci/circleci: core-tests
  • check-success=ci/circleci: demo-tests
  • check-success=ci/circleci: yarn-monorepo
  • check-success=license/cla
  • label!=do-not-merge
  • label!=mergify-ignore
• -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: Add merge train label (comment, label)

• queue-position >= 0

✅ Rule: Remove merge train label (label)

• queue-position = -1

Rule: Ask to resolve conflict (comment, label)

• conflict

✅ Rule: Remove conflicts label when conflicts gone (label)

• -conflict

Rule: Notify author when added to merge queue (comment)

• check-pending=Queue: Embarked in merge train

Rule: Notify author when merge queue failed (comment)

• check-failure=Queue: Embarked in merge train

Rule: Nag changesets (comment)

• all of:
  • files~=\.((?<!\.spec\.)ts|js|sol)$
  • -files~=^\.changeset/(.*)\.md

---

💖  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 on approval (develop) (queue)

• all of:
  • #approved-reviews-by>=1
  • base=develop
  • check-success=ci/circleci: executor-tests
  • check-success=ci/circleci: plugins-tests
  • #changes-requested-reviews-by=0
  • #review-threads-unresolved=0
  • check-success=ci/circleci: contracts-tests
  • check-success=ci/circleci: core-tests
  • check-success=ci/circleci: demo-tests
  • check-success=ci/circleci: yarn-monorepo
  • check-success=license/cla
  • label!=do-not-merge
  • label!=mergify-ignore
• -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]

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