Rule: Add needs-dco label when DCO check failed (label)

• -status-success=DCO
• any of:
  • base=dev
  • base=main

✅ Rule: Add dco-passed label when DCO check passed (label)

• status-success=DCO
• any of:
  • base=dev
  • base=main

Rule: Test passed for code changed (label)

• status-success=build-pypi
• status-success=codecov/patch
• status-success=codecov/project
• status-success=pylint
• status-success=unit-test-main
• any of:
  • base=dev
  • base=main

Rule: Test passed for title skip ci (label)

• -files~=^(?=.*((\.(sh|py)|Makefile))).*$
• title~=\[skip ci\]
• any of:
  • base=dev
  • base=main

Rule: Test passed for markdown file (label)

• files=^.*\.md$
• any of:
  • base=dev
  • base=main

✅ Rule: Remove ci-passed label when ut failed for main (label)

• files~=^(?=.*((\.(sh|py)|Makefile))).*$
• any of:
  • base=dev
  • base=main
• any of:
  • status-success!=build-pypi
  • status-success!=pylint
  • status-success!=unit-test-main

---

💖  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