[2.9.x] Patch updates #332
3 rules match and 3 potential rules
The configuration uses the deprecated
update_method
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_rules
configuration.
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_method
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_rules
configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
Rule: Merge PRs that are ready (queue)
-
#approved-reviews-by>=1
-
-closed
[π queue requirement] -
label=status:merge-when-green
-
#changes-requested-reviews-by=0
-
#review-requested=0
-
-conflict
[π queue requirement] -
-draft
[π queue requirement] -
check-success~=/ Ready To Merge$
-
label!=status:block-merge
- 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 = Finish / Ready To Merge
-
check-neutral = Finish / Ready To Merge
-
check-skipped = Finish / Ready To Merge
-
- any of: [π‘ GitHub branch protection]
- all of: [π queue conditions of queue
Rule: Merge (Rebase) PRs that are ready (queue)
-
#approved-reviews-by>=1
-
-closed
[π queue requirement] -
label=status:merge-rebase-when-green
-
#changes-requested-reviews-by=0
-
#review-requested=0
-
-conflict
[π queue requirement] -
-draft
[π queue requirement] -
check-success~=/ Ready To Merge$
-
label!=status:block-merge
- 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 = Finish / Ready To Merge
-
check-neutral = Finish / Ready To Merge
-
check-skipped = Finish / Ready To Merge
-
- any of: [π‘ GitHub branch protection]
- all of: [π queue conditions of queue
Rule: Merge (Squash) PRs that are ready (queue)
-
#approved-reviews-by>=1
-
-closed
[π queue requirement] -
label=status:merge-squash-when-green
-
#changes-requested-reviews-by=0
-
#review-requested=0
-
-conflict
[π queue requirement] -
-draft
[π queue requirement] -
check-success~=/ Ready To Merge$
-
label!=status:block-merge
- 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 = Finish / Ready To Merge
-
check-neutral = Finish / Ready To Merge
-
check-skipped = Finish / Ready To Merge
-
- any of: [π‘ GitHub branch protection]
- all of: [π queue conditions of queue
β Rule: Delete the PR branch and remove label after merge/close (delete_head_branch)
-
closed
[π delete_head_branch requirement] - any of:
-
closed
-
merged
-
β Rule: Delete the PR branch and remove label after merge/close (label)
- any of:
-
closed
-
merged
-
β Rule: Labeling for Scala Steward PR's (label)
-
author=scala-steward
πΒ Β 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