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

Rule: Test passed for code changed (label)

• status-success=Unittest AMD64 Ubuntu 18.04
• status-success=Run Ci Test (cluster)
• status-success=Run Ci Test (standalone)
• status-success=lint
• any of:
  • base=master
  • base~=^v2(\.\d+).x$

✅ Rule: Test passed for e2e changed (label)

• -files~=^(?!test\/).+
• status-success=Run Ci Test (cluster)
• status-success=Run Ci Test (standalone)
• status-success=lint
• any of:
  • base=master
  • base~=^v2(\.\d+).x$

Rule: Test passed for mergify changed (label)

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

Rule: Test passed for workflow changed (label)

• -files~=^(?!\.github\/).+
• any of:
  • base=master
  • base~=^v2(\.\d+).x$

Rule: Test passed for example code changed (label)

• -files~=^(?!examples\/).+
• status-success=lint
• any of:
  • base=master
  • base~=^v2(\.\d+).x$

Rule: Remove ci-passed when some test failed (label)

• any of:
  • check-failure=Unittest AMD64 Ubuntu 18.04
  • check-failure=lint
• any of:
  • base=master
  • base~=^v2(\.\d+).x$

Rule: Remove ci-passed when some test failed for branch (label)

• any of:
  • check-failure=Run Ci Test (cluster)
  • check-failure=Run Ci Test (standalone)
  • check-failure=Unittest AMD64 Ubuntu 18.04
  • check-failure=lint
• any of:
  • base=master
  • base~=^v2(\.\d+).x$

---

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

🚀  You can help us by becoming a sponsor!

---

3 not applicable rules

Rule: Test passed for document changed (label)

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

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

• base=.+
• -body~=\#[0-9]{1,6}(\s+|$)
• -label=kind/improvement
• -title~=\[automated\]

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

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

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