feat(server/v2): init the indexer in server/v2 (partial backport #22218) #22324
no rules match, no planned actions
The configuration uses the deprecated
commit_message_template
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 September 16th, 2024.
This option will be removed on October 21st, 2024.
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.
A brownout is planned on September 16th, 2024.
This option will be removed on October 21st, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
6 not applicable rules
Rule: automerge to main with label automerge and branch protection passing (queue)
-
#approved-reviews-by>1
-
-closed
[📌 queue requirement] -
base=main
-
label=A:automerge
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]- any of: [🛡 GitHub branch protection]
-
check-neutral = test-system
-
check-skipped = test-system
-
check-success = test-system
-
-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] -
branch-protection-review-decision = APPROVED
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success = tests (00)
-
check-neutral = tests (00)
-
check-skipped = tests (00)
-
- any of: [🛡 GitHub branch protection]
-
check-success = tests (01)
-
check-neutral = tests (01)
-
check-skipped = tests (01)
-
- any of: [🛡 GitHub branch protection]
-
check-success = tests (02)
-
check-neutral = tests (02)
-
check-skipped = tests (02)
-
- any of: [🛡 GitHub branch protection]
-
check-success = tests (03)
-
check-neutral = tests (03)
-
check-skipped = tests (03)
-
- any of: [🛡 GitHub branch protection]
-
check-success = test-e2e
-
check-neutral = test-e2e
-
check-skipped = test-e2e
-
- any of: [🛡 GitHub branch protection]
-
check-success = test-integration
-
check-neutral = test-integration
-
check-skipped = test-integration
-
- any of: [🛡 GitHub branch protection]
-
check-success = golangci-lint
-
check-neutral = golangci-lint
-
check-skipped = golangci-lint
-
- any of: [🛡 GitHub branch protection]
-
check-success = build (amd64)
-
check-neutral = build (amd64)
-
check-skipped = build (amd64)
-
- any of: [🛡 GitHub branch protection]
-
check-success = build (arm64)
-
check-neutral = build (arm64)
-
check-skipped = build (arm64)
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
-
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
Rule: backport patches to v0.52.x branch (backport)
-
base=main
-
label=backport/v0.52.x
-
merged
[📌 backport requirement]
Rule: backport patches to v0.50.x branch (backport)
-
base=main
-
label=backport/v0.50.x
-
merged
[📌 backport requirement]
Rule: backport patches to v0.47.x branch (backport)
-
base=main
-
label=backport/v0.47.x
-
merged
[📌 backport requirement]
Rule: backport patches to v0.46.x branch (backport)
-
base=main
-
label=backport/0.46.x
-
merged
[📌 backport requirement]
Rule: backport patches to v0.45.x branch (backport)
-
base=main
-
label=backport/0.45.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 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