Rule: automatic merge with 2 reviews (queue)

• status-success=Jenkins - TensorRT Unit tests GPU
• #changes-requested-reviews-by=0
• -draft [📌 queue requirement]
• base=master
• label!=process:manual-merge
• status-success=Jenkins - Unit tests GPU
• any of:
  • label!=ci:docker
  • status-success=Jenkins - Docker build
• any of:
  • all of:
    • #approved-reviews-by>=2
    • label=process:ready-to-review
  • label=process:no-need-review
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed
• any of: [🔀 queue conditions]
  • all of [📌 queue conditions of queue default]

Rule: request review (request_reviews)

• #approved-reviews-by=0
• #changes-requested-reviews-by=0
• -closed
• -merged
• label=process:ready-to-review

Rule: warn on conflicts (comment, label)

• conflict

✅ Rule: remove conflict label if not needed (label)

• -conflict

Rule: add ci:docker label (label)

• files~=^docker/

Rule: add merge-queued label (label)

• queue-position>=0

✅ Rule: remove merge-queued label (label)

• queue-position<0

---

💖  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