fix(tianmu): provide error information for "create constraint and foreign keys"(not supported) #1838
Mergify / Summary
succeeded
Nov 23, 2023 in 0s
2 rules match and 12 potential rules
Rule: automatic merge of hotfix (high priority) (queue)
-
#approved-reviews-by>=2
-
check-success~=^stonedb-build(.*)
- any of: [:twisted_rightwards_arrows: queue conditions]
- all of: [:pushpin: queue conditions of queue
shared_queue
]-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
branch-protection-review-decision=APPROVED
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection]
-
- all of: [:pushpin: queue conditions of queue
-
-draft
[:pushpin: queue requirement] -
-mergify-configuration-changed
[:pushpin: queue -> allow_merging_configuration_change setting requirement] -
label!=PR-docs
-
label=PR-bug
Rule: put other pr to merge queue (queue)
-
#approved-reviews-by>=2
-
check-success~=^stonedb-build(.*)
-
label!=PR-bug
- any of: [:twisted_rightwards_arrows: queue conditions]
- all of: [:pushpin: queue conditions of queue
shared_queue
]-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
branch-protection-review-decision=APPROVED
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection]
-
- all of: [:pushpin: queue conditions of queue
-
-draft
[:pushpin: queue requirement] -
-mergify-configuration-changed
[:pushpin: queue -> allow_merging_configuration_change setting requirement] -
label!=PR-docs
Rule: put docs to merge queue (queue)
-
#approved-reviews-by>=2
-
label=PR-docs
- any of: [:twisted_rightwards_arrows: queue conditions]
- all of: [:pushpin: queue conditions of queue
shared_queue
]-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
branch-protection-review-decision=APPROVED
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection]
-
- all of: [:pushpin: queue conditions of queue
-
-draft
[:pushpin: queue requirement] -
-mergify-configuration-changed
[:pushpin: queue -> allow_merging_configuration_change setting requirement]
Rule: Comment PR if title not semantic (comment)
-
-title~=^(feat|fix|docs|workflow|perf|style|refactor|test|website|chore)(\(.*\))?:
-
author!=Mergify
Rule: ping author if there is conflicts (comment)
-
#approved-reviews-by >= 2
-
conflict
Rule: Welcome new contributor (comment)
-
author!=Mergify
Rule: label on New Feature (label)
-
title~=^(feat)(\(.*\))?:
Rule: label on Bug Fix (label)
-
title~=^(fix)(\(.*\))?:
Rule: label on docs (label)
-
title~=^(docs)(\(.*\))?:
Rule: label on perf (label)
-
title~=^(perf)(\(.*\))?:
Rule: label on style (label)
-
title~=^(style)(\(.*\))?:
Rule: label on Refactor (label)
-
title~=^(refactor)(\(.*\))?:
Rule: label on test (label)
-
title~=^(test)(\(.*\))?:
Rule: label on chore (label)
-
title~=^(chore)(\(.*\))?:
💖 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