Release of version 4.6.0 #117
Merged
Mergify / Summary
succeeded
May 23, 2024 in 1s
1 potential rule
Rule: Automatic merge on approval & CI (queue)
-
check-success=Windows - all of:
-
label=ready-to-merge -
#approved-reviews-by>=1 -
#changes-requested-reviews-by=0 -
#review-requested=0
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default]- any of: [🛡 GitHub branch protection]
-
check-neutral=Windows -
check-skipped=Windows -
check-success=Windows
-
-
#approved-reviews-by>=1[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=Ubuntu 20 -
check-neutral=Ubuntu 20 -
check-skipped=Ubuntu 20
-
- any of: [🛡 GitHub branch protection]
-
check-success=Ubuntu 22 -
check-neutral=Ubuntu 22 -
check-skipped=Ubuntu 22
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
-
-draft[📌 queue requirement] -
check-success=Ubuntu 20 -
check-success=Ubuntu 22 - 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
Loading