Add code coverage check#1929
Merged
Merged
Mergify / Summary
succeeded
Jun 25, 2026 in 1s
2 rules match and 3 potential rules
Rule: Add needs-dco label when DCO check failed (label)
-
-status-success=DCO - any of:
-
base~=2\.\d -
base=3.0 -
base=master
-
✅ Rule: Add dco-passed label when DCO check passed (label)
-
status-success=DCO - any of:
-
base~=2\.\d -
base=3.0 -
base=master
-
✅ Rule: Test passed for CI-required changes (label)
-
files~=^(?!(doc/|benchmark/|examples/|.*\.md$|(.*/)?OWNERS$|LICENSE$)) -
status-success=Build and test - any of:
-
base~=2\.\d -
base=3.0 -
base=master
-
Rule: Add ci-passed for CI-skipped changes (label)
-
-files~=^(?!(doc/|benchmark/|examples/|.*\.md$|(.*/)?OWNERS$|LICENSE$)) -
files~=^(doc/|benchmark/|examples/|.*\.md$|(.*/)?OWNERS$|LICENSE$) - any of:
-
base~=2\.\d -
base=3.0 -
base=master
-
Rule: Remove ci-passed when required check is not successful (label)
-
-status-success=Build and test -
files~=^(?!(doc/|benchmark/|examples/|.*\.md$|(.*/)?OWNERS$|LICENSE$)) - any of:
-
base~=2\.\d -
base=3.0 -
base=master
-
💖 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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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
Loading