⚠️ The pull request has been merged by @sre-ci-robot

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-main (label)

• check-success=Backup and restore after upgrade (docker-compose, standalone, standalone, 2.4-latest, 2.5-latest)
• check-success=Backup and restore after upgrade (docker-compose, standalone, standalone, 2.4-latest, master-latest)
• check-success=Backup and restore after upgrade (docker-compose, standalone, standalone, 2.5-latest, master-latest)
• check-success=Backup and restore api (docker-compose, standalone, 2.5-latest, L0)
• check-success=Backup and restore api (docker-compose, standalone, 2.5-latest, L1)
• check-success=Backup and restore api (docker-compose, standalone, 2.5-latest, L2)
• check-success=Backup and restore api (docker-compose, standalone, master-latest, L0)
• check-success=Backup and restore api (docker-compose, standalone, master-latest, L1)
• check-success=Backup and restore api (docker-compose, standalone, master-latest, L2)
• check-success=Backup and restore api (docker-compose, standalone, master-latest, MASTER)
• check-success=Backup and restore cli (docker-compose, standalone, standalone, master-latest)
• check-success=Backup and restore cross version (docker-compose, standalone, standalone, 2.4-latest, 2.5-latest)
• check-success=Backup and restore cross version (docker-compose, standalone, standalone, 2.5-latest, master-latest)
• check-success=Backup and restore cross version (docker-compose, standalone, standalone, 2.5-latest, master-latest)
• check-success=Backup and restore cross version (docker-compose, standalone, standalone, v2.2.16, 2.5-latest)
• check-success=Backup and restore cross version (docker-compose, standalone, standalone, v2.2.16, master-latest)
• check-success=Backup and restore cross version (docker-compose, standalone, standalone, v2.3.22, 2.5-latest)
• check-success=Backup and restore cross version (docker-compose, standalone, standalone, v2.3.22, master-latest)
• check-success=Backup and restore with rbac config (helm, standalone, master-latest)
• check-success=Unit test go

Rule: Test passed for non-code changed (label)

• any of:
  • -files~=^(?!.*\.(md)).*$
  • -files~=^(?!docs\/).+
  • -files~=^(?!scripts\/).+
• base=main

Rule: Test passed for mergify changed (label)

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

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

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

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

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

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

• title~=\[automated\]
• base=main

Rule: Remove ci-passed label when status for code checker or ut is not success-main (label)

• any of:
  • check-success!=Backup and restore after upgrade (docker-compose, standalone, standalone, 2.4-latest, 2.5-latest)
  • check-success!=Backup and restore after upgrade (docker-compose, standalone, standalone, 2.4-latest, master-latest)
  • check-success!=Backup and restore after upgrade (docker-compose, standalone, standalone, 2.5-latest, master-latest)
  • check-success!=Backup and restore api (docker-compose, standalone, 2.5-latest, L0)
  • check-success!=Backup and restore api (docker-compose, standalone, 2.5-latest, L1)
  • check-success!=Backup and restore api (docker-compose, standalone, 2.5-latest, L2)
  • check-success!=Backup and restore api (docker-compose, standalone, master-latest, L0)
  • check-success!=Backup and restore api (docker-compose, standalone, master-latest, L1)
  • check-success!=Backup and restore api (docker-compose, standalone, master-latest, L2)
  • check-success!=Backup and restore api (docker-compose, standalone, master-latest, MASTER)
  • check-success!=Backup and restore cli (docker-compose, standalone, standalone, master-latest)
  • check-success!=Backup and restore cross version (docker-compose, standalone, standalone, 2.4-latest, 2.5-latest)
  • check-success!=Backup and restore cross version (docker-compose, standalone, standalone, 2.4-latest, master-latest)
  • check-success!=Backup and restore cross version (docker-compose, standalone, standalone, 2.5-latest, master-latest)
  • check-success!=Backup and restore with rbac config (helm, standalone, master-latest)
  • check-success!=Unit test go
• base=main
• files~=^(?=.*((\.(go|h|cpp)|CMakeLists.txt))).*$
• label!=manual-pass

---

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

---

1 not applicable rule

Rule: Add kind/improvement tag for dependabot's PR (label)

• author=dependabot[bot]
• base=main

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