Rule: refactored queue action rule (queue)

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #changes-requested-reviews-by=0
    • base=main
    • check-success=DCO
    • check-success=build-binaries (tink-agent, cross-compile-agent, tink-agent-binaries)
    • check-success=build-binaries (tinkerbell, cross-compile, tinkerbell-binaries)
    • check-success=validation
    • label!=do-not-merge
    • label=ready-to-merge
    • any of:
      • author=jacobweinstock
      • #approved-reviews-by>=1
    • any of: [🛡 GitHub branch protection]
      • check-success = DCO
      • check-neutral = DCO
      • check-skipped = DCO
    • any of: [🛡 GitHub branch protection]
      • check-success = validation
      • check-neutral = validation
      • check-skipped = validation
    • any of: [🛡 GitHub branch protection]
      • check-success = build-binaries (tink-agent, cross-compile-agent, tink-agent-binaries)
      • check-neutral = build-binaries (tink-agent, cross-compile-agent, tink-agent-binaries)
      • check-skipped = build-binaries (tink-agent, cross-compile-agent, tink-agent-binaries)
    • any of: [🛡 GitHub branch protection]
      • check-success = build-binaries (tinkerbell, cross-compile, tinkerbell-binaries)
      • check-neutral = build-binaries (tinkerbell, cross-compile, tinkerbell-binaries)
      • check-skipped = build-binaries (tinkerbell, cross-compile, tinkerbell-binaries)
    • any of: [🛡 GitHub repository ruleset rule]
      • check-success = validation
      • check-neutral = validation
      • check-skipped = validation

---

💖  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