‼️ 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: automatic merge for master when CI passes and approved (queue)

• #approved-reviews-by>=1
• -closed [📌 queue requirement]
• #changes-requested-reviews-by=0
• #commented-reviews-by=0
• #review-requested=0
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• base=master
• status-success=jslint
• status-success=lint
• status-success=mypy
• status-success=test
• 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 = jslint
      • check-neutral = jslint
      • check-skipped = jslint
    • any of: [🛡 GitHub branch protection]
      • check-success = lint
      • check-neutral = lint
      • check-skipped = lint
    • any of: [🛡 GitHub branch protection]
      • check-success = mypy
      • check-neutral = mypy
      • check-skipped = mypy
    • any of: [🛡 GitHub branch protection]
      • check-success = test
      • check-neutral = test
      • check-skipped = test

Rule: automatic merge for master when CI passes and trusted comitter (queue)

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• author=@PennyDreadfulMTG/automerge
• base=master
• status-success=jslint
• status-success=lint
• status-success=mypy
• status-success=test
• 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 = jslint
      • check-neutral = jslint
      • check-skipped = jslint
    • any of: [🛡 GitHub branch protection]
      • check-success = lint
      • check-neutral = lint
      • check-skipped = lint
    • any of: [🛡 GitHub branch protection]
      • check-success = mypy
      • check-neutral = mypy
      • check-skipped = mypy
    • any of: [🛡 GitHub branch protection]
      • check-success = test
      • check-neutral = test
      • check-skipped = test

---

💖  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: automatic merge dependency updates (delete_head_branch)

• author~=(pyup-bot|dependabot)
• -files~=^(!?.github/workflows/)
• closed [📌 delete_head_branch requirement]
• status-success=jslint
• status-success=lint
• status-success=mypy
• status-success=test

Rule: automatic merge dependency updates (merge)

• -closed [📌 merge requirement]
• author~=(pyup-bot|dependabot)
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• -files~=^(!?.github/workflows/)
• status-success=jslint
• status-success=lint
• status-success=mypy
• status-success=test
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🛡 GitHub branch protection]
  • check-success = jslint
  • check-neutral = jslint
  • check-skipped = jslint
• any of: [🛡 GitHub branch protection]
  • check-success = lint
  • check-neutral = lint
  • check-skipped = lint
• any of: [🛡 GitHub branch protection]
  • check-success = mypy
  • check-neutral = mypy
  • check-skipped = mypy
• any of: [🛡 GitHub branch protection]
  • check-success = test
  • check-neutral = test
  • check-skipped = test

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