fix: update swap keys for possibly overlapped keys (backport #1365) #1367
Mergify / Summary
succeeded
May 8, 2024 in 1s
1 rule matches
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
4 not applicable rules
Rule: automerge to main with label automerge and branch protection passing (queue)
-
base=main -
label=automerge -
#approved-reviews-by>1 -
-draft[📌 queue requirement] - 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>=2[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0[🛡 GitHub branch protection] -
#review-threads-unresolved=0[🛡 GitHub branch protection]
-
- all of: [📌 queue conditions of queue
Rule: backport patches to v0.49.x branch (backport)
-
base=main -
label=backport/v0.49.x -
merged[📌 backport requirement]
Rule: backport patches to v0.48.x branch (backport)
-
base=main -
label=backport/v0.48.x -
merged[📌 backport requirement]
Rule: backport patches to v0.47.x branch (backport)
-
base=main -
label=backport/v0.47.x -
merged[📌 backport requirement]
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