refactor: step 4 #29
Merged
refactor: step 4 #29
Mergify / Summary
succeeded
Nov 18, 2024 in 0s
1 rule matches and 3 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.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
✅ Rule: Put PRs in queue (squash) (delete_head_branch)
-
#approved-reviews-by>=1
-
-label~=(do-not-merge)
-
base = main
-
closed
[📌 delete_head_branch requirement] -
status-success=build
Rule: Put PRs in queue (squash) (queue)
-
-closed
[📌 queue requirement] -
#approved-reviews-by>=1
-
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] -
-label~=(do-not-merge)
-
base = main
-
status-success=build
- 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: Label core contributions (label)
-
label!=contribution/core
-
author~=^(pgollucci)$
Rule: Label auto-merge for core (label)
-
label!=auto-merge
-
label=contribution/core
💖 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