Add message_info and deprecate mock_info (backport #2160) #2161
Mergify / Summary
succeeded
Jun 3, 2024 in 1s
1 rule matches
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
2 not applicable rules
Rule: automerge to main with label automerge (merge)
-
-closed[📌 merge requirement] -
base=main -
label=automerge -
status-success=ci/circleci: clippy-1.67.0 -
status-success=ci/circleci: clippy-1.68.2 -
status-success=ci/circleci: contract_floaty -
#approved-reviews-by>=1 -
#approved-reviews-by>=1[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0[🛡 GitHub branch protection] -
-conflict[📌 merge requirement] -
-draft -
-draft[📌 merge requirement] -
label!=WIP -
status-success=Windows -
status-success=ci/circleci: arm64 -
status-success=ci/circleci: contract_burner -
status-success=ci/circleci: contract_crypto_verify -
status-success=ci/circleci: contract_cyberpunk -
status-success=ci/circleci: contract_hackatom -
status-success=ci/circleci: contract_hackatom -
status-success=ci/circleci: contract_ibc_reflect -
status-success=ci/circleci: contract_ibc_reflect_send -
status-success=ci/circleci: contract_queue -
status-success=ci/circleci: contract_reflect -
status-success=ci/circleci: contract_staking -
status-success=ci/circleci: contract_virus -
status-success=ci/circleci: fmt -
status-success=ci/circleci: fmt_extra -
status-success=ci/circleci: package_check -
status-success=ci/circleci: package_crypto -
status-success=ci/circleci: package_schema -
status-success=ci/circleci: package_schema_derive -
status-success=ci/circleci: package_std -
status-success=ci/circleci: package_vm -
status-success=ci/circleci: package_vm_windows -
status-success=macOS - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success=Configuration changed
-
Rule: backport PRs to minor version branch (backport)
-
base=main -
label=backport -
merged[📌 backport requirement]
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