⚠️ The pull request has been merged by @SimFG

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

• -status-success=DCO
• any of:
  • base=master
  • base~=^2(\.\d+){1,2}$

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

• status-success=DCO
• any of:
  • base=master
  • base~=^2(\.\d+){1,2}$

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-proto/issues/[0-9]{1,6}(\s+|$)
• -body~=https://github.com/milvus-io/milvus/issues/[0-9]{1,6}(\s+|$)
• -label=kind/improvement
• -title~=\[automated\]
• any of:
  • base=master
  • base~=^2(\.\d+){1,2}$

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

• any of:
  • all of:
    • any of:
      • base=master
      • base~=^2(\.\d+){1,2}$
    • any of:
      • body~=\#[0-9]{1,6}(\s+|$)
      • body~=https://github.com/milvus-io/milvus-proto/issues/[0-9]{1,6}(\s+|$)
      • body~=https://github.com/milvus-io/milvus/issues/[0-9]{1,6}(\s+|$)
  • all of:
    • label=kind/improvement
    • base=master

Rule: Dismiss block label if automated create PR (label)

• title~=\[automated\]
• any of:
  • base=master
  • base~=^2(\.\d+){1,2}$

✅ Rule: Test passed for code changed (label)

• status-success=Run Check Proto (3.8)
• any of:
  • base=master
  • base~=^2(\.\d+){1,2}$

Rule: Remove ci-passed label when test is not passed (label)

• status-success!=Run Check Proto (3.8)
• any of:
  • base=master
  • base~=^2(\.\d+){1,2}$

---

💖  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