⬆️ Bump mlua from 0.9.8 to 0.9.9 #583
Merged
Mergify / Summary
succeeded
Aug 16, 2024 in 0s
1 rule matches and 2 potential rules
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
### Rule: Automatic merge on approval (queue)
-
#approved-reviews-by>=2
-
-draft
[📌 queue requirement] -
check-success=CodeFactor
-
check-success=Rust project
-
check-success=build (stable)
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection] -
#review-threads-unresolved=0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=build (stable)
-
check-neutral=build (stable)
-
check-skipped=build (stable)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Rust project
-
check-neutral=Rust project
-
check-skipped=Rust project
-
- any of: [🛡 GitHub branch protection]
-
check-success=CodeFactor
-
check-neutral=CodeFactor
-
check-skipped=CodeFactor
-
-
- all of: [📌 queue conditions of queue
Rule: automatic update of pull requests where more 5 commits behind (update)
-
#commits-behind>0
[📌 update requirement] -
#commits-behind>5
-
-closed
[📌 update requirement] -
-conflict
[📌 update requirement] -
queue-position=-1
[📌 update requirement]
✅ Rule: delete head branch after merge (delete_head_branch)
-
closed
[📌 delete_head_branch requirement] -
merged
💖 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