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

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

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

• author=BiocondaBot
• check-success=Linux Tests
• check-success=OSX Tests
• created-at<3 days ago
• label=autobump
• #commits=1

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