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

• -status-success=DCO
• base=main

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

• base=main
• status-success=DCO

Rule: Test passed for code changed (label)

• status-success=Unittest AMD64 Ubuntu 18.04
• base=main

Rule: Test passed for document changed (label)

• -files~=\.(?!md|png)
• -files~=^[^\.]+$
• base=main

Rule: Test passed for mergify changed (label)

• -files~=^(?!\.github\/mergify\.yml).*$
• base=main

Rule: Remove ci-passed when unittest failed (label)

• check-failure=Unittest AMD64 Ubuntu 18.04
• base=main
• files~=\.(?!md|png)
• files~=^(?!\.github\/mergify\.yml).*$

Rule: Blocking PR if missing a related issue or PR doesn't have kind/improvement label (comment, label)

• -body~=\#[0-9]{1,6}(\s+|$)
• -body~=https://github.com/milvus-io/milvus-sdk-rust/issues/[0-9]{1,6}(\s+|$)
• -label=kind/improvement
• -title~=\[automated\]
• base=main

✅ Rule: Dismiss block label if related issue be added into PR (label)

• any of:
  • all of:
    • base=main
    • any of:
      • body~=\#[0-9]{1,6}(\s+|$)
      • body~=https://github.com/milvus-io/milvus-sdk-rust/issues/[0-9]{1,6}(\s+|$)
  • all of:
    • label=kind/improvement
    • base=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