Rule: Automatic merge PR with automerge label (merge)

• check-success=Django tests (3.10)
• check-success=Django tests (3.9)
• label=automerge
• -closed [📌 merge requirement]
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• check-success=BI Validate
• check-success=Build Prod Image
• check-success=Static checks
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed
• any of: [🛡 GitHub branch protection]
  • check-success=Build Prod Image
  • check-neutral=Build Prod Image
  • check-skipped=Build Prod Image
• any of: [🛡 GitHub branch protection]
  • check-success=Static checks
  • check-neutral=Static checks
  • check-skipped=Static checks
• any of: [🛡 GitHub branch protection]
  • check-success=BI Validate
  • check-neutral=BI Validate
  • check-skipped=BI Validate

Rule: Add label on conflict (comment, label)

• conflict
• -closed

✅ Rule: Remove label on conflict (label)

• -closed
• -conflict

Rule: Add label on BI Validatiton failutre (label)

• check-failure=BI Validate

✅ Rule: Remove label on BI Validatiton success (label)

• check-success=BI Validate

---

💖  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