Rule: refactored queue action rule (queue)

• -closed [📌 queue requirement]
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • author=dependabot[bot]
    • status-success=codeclimate/diff-coverage
    • status-success=codeclimate/total-coverage
    • status-success=cypress: all tests
    • any of: [🛡 GitHub branch protection]
      • check-neutral = cypress: all tests
      • check-skipped = cypress: all tests
      • check-success = cypress: all tests
    • any of: [🛡 GitHub branch protection]
      • check-neutral = default
      • check-skipped = default
      • check-success = default
    • #changes-requested-reviews-by=0
    • status-success=Vercel – operation-code
    • status-success=Vercel – storybook
    • status-success=ci/circleci: lint
    • status-success=ci/circleci: unit_tests
    • any of: [🛡 GitHub branch protection]
      • check-success = Vercel – operation-code
      • check-neutral = Vercel – operation-code
      • check-skipped = Vercel – operation-code
    • any of: [🛡 GitHub branch protection]
      • check-success = Vercel – storybook
      • check-neutral = Vercel – storybook
      • check-skipped = Vercel – storybook
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

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