Rule: Approve and merge autobump PRs if tests are successful (merge)

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
• #commits=1
• -closed [📌 merge requirement]
• author=BiocondaBot
• created-at<3 days ago
• label=autobump
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• check-success=Linux Tests
• check-success=OSX-64 Tests
• check-success=build and test (ARM)
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🛡 GitHub branch protection]
  • check-success = Linux Tests
  • check-neutral = Linux Tests
  • check-skipped = Linux Tests
• any of: [🛡 GitHub branch protection]
  • check-success = Lint
  • check-neutral = Lint
  • check-skipped = Lint
• any of: [🛡 GitHub branch protection]
  • check-success = OSX-64 Tests
  • check-neutral = OSX-64 Tests
  • check-skipped = OSX-64 Tests

Rule: Approve and merge autobump PRs if tests are successful (review)

• #commits=1
• author=BiocondaBot
• created-at<3 days ago
• label=autobump
• check-success=Linux Tests
• check-success=OSX-64 Tests
• check-success=build and test (ARM)

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