registering statik namespace with "terrad" #536
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!
2 not applicable rules
Rule: automerge to main with label automerge and branch protection passing (queue)
-
#approved-reviews-by>2 -
-closed[📌 queue requirement] -
base=main -
label=A:automerge -
-conflict[📌 queue requirement] -
-draft[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [🔀 queue conditions]
- all of [📌 queue conditions of queue
default]
- all of [📌 queue conditions of queue
Rule: backport patches to v2.1.x branch (backport)
-
base=main -
label=backport/v2.1.x -
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