fix handling of cargo.lock outside a workspace #273
1 potential rule
The configuration uses the deprecated
merge_method
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_rules
configuration.
A brownout is planned on August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
The configuration uses the deprecated
allow_merging_configuration_change
attribute of the queue action in one or morepull_request_rules
. It must be removed from the configuration.
A brownout is planned on August 26th, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
Rule: merge using the merge queue (queue)
-
label~=merge-queue|dependencies
-
-draft
[📌 queue requirement] -
base=master
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]- any of: [🛡 GitHub branch protection]
-
check-success=tests
-
check-neutral=tests
-
check-skipped=tests
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
💖 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