Implement MilvusClientV2 (2.6) - #141

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

• -status-success=DCO
• any of:
  • base=main
  • base~=2\.\d

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

• status-success=DCO
• any of:
  • base=main
  • base~=2\.\d

Rule: Test passed for code changed (label)

• all of:
  • check-success=Build and test with Milvus v2.3.22
  • check-success=Build and test with Milvus v2.4.23
  • check-success=Build and test with Milvus v2.5.20
  • check-success=Build and test with Milvus v2.6.4
• any of:
  • base=main
  • base~=2\.\d

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

• any of:
  • check-failure=Build and test with Milvus v2.3.22
  • check-failure=Build and test with Milvus v2.4.23
  • check-failure=Build and test with Milvus v2.5.20
  • check-failure=Build and test with Milvus v2.6.4
• any of:
  • base=main
  • base~=2\.\d

Rule: Add ci-passed when no code changes (label)

• -files~=^(?!.*\.(md)).*$
• any of:
  • base=main
  • base~=2\.\d

---

💖  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