Rule: Automatic merge (queue)

• label=ready-to-merge
• all of:
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • base=main
  • check-success=DCO
  • check-success=Package (quay.io/tinkerbell/tink, tink-server)
  • check-success=Package (quay.io/tinkerbell/tink-controller, tink-controller)
  • check-success=Package (quay.io/tinkerbell/tink-worker, tink-worker)
  • label!=do-not-merge
• any of: [:twisted_rightwards_arrows: queue conditions]
  • all of: [:pushpin: queue conditions of queue default]
    • #approved-reviews-by>=1 [🛡 GitHub branch protection]
    • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success=DCO
      • check-neutral=DCO
      • check-skipped=DCO
• -draft [:pushpin: queue requirement]
• -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]

---

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

---

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