Add skeleton for test_engine_crash_during_live_upgrade #1712
Mergify / Summary
succeeded
Feb 26, 2024 in 1s
2 potential rules
Rule: automatic merge after review (merge)
-
#approved-reviews-by>=2
-
-closed
[📌 merge requirement] -
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection] -
#commits-behind=0
[🛡 GitHub branch protection] -
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] -
approved-reviews-by=@longhorn/maintainer
-
check-success=CodeFactor
-
check-success=DCO
-
check-success=codespell
-
check-success=continuous-integration/drone/pr
- any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success=DCO
-
check-neutral=DCO
-
check-skipped=DCO
-
- any of: [🛡 GitHub branch protection]
-
check-success=continuous-integration/drone/pr
-
check-neutral=continuous-integration/drone/pr
-
check-skipped=continuous-integration/drone/pr
-
Rule: ask to resolve conflict (comment)
-
conflict
💖 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
Loading