chore!: replace NMTProof with Proof in nmt #1432
no rules match, no planned actions
The configuration uses the deprecated
commit_message_templateattribute of the queue action in one or morepull_request_rules. It must now be used under thequeue_rulesconfiguration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
The configuration uses the deprecated
merge_methodattribute of the queue action in one or morepull_request_rules. It must now be used under thequeue_rulesconfiguration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
1 not applicable rule
Rule: Automerge to v0.34.x-celestia (queue)
-
base=v0.34.x-celestia -
label=S:automerge - any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default]-
#approved-reviews-by >= 2[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-neutral = e2e-test -
check-skipped = e2e-test -
check-success = e2e-test
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = tests (01) -
check-skipped = tests (01) -
check-success = tests (01)
-
-
#changes-requested-reviews-by = 0[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success = tests (00) -
check-neutral = tests (00) -
check-skipped = tests (00)
-
- any of: [🛡 GitHub branch protection]
-
check-success = tests (02) -
check-neutral = tests (02) -
check-skipped = tests (02)
-
- any of: [🛡 GitHub branch protection]
-
check-success = tests (03) -
check-neutral = tests (03) -
check-skipped = tests (03)
-
-
- all of: [📌 queue conditions of queue
-
-closed[📌 queue requirement] -
-conflict[📌 queue requirement] -
-draft[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
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