Update merge queue configuration - #10
Conversation
Signed-off-by: Konstantin <null>
| - "#approved-reviews-by >= 1" | ||
| merge_conditions: | ||
| - "#check-success >= 2" | ||
| merge_queue: |
There was a problem hiding this comment.
WARNING: merge_queue: / max_parallel_checks does not appear to be a valid Mergify configuration key
Mergify controls merge-queue parallelism via speculative_checks (and batch_size) declared inside each queue_rules entry, not via a top-level merge_queue block. This merge_queue/max_parallel_checks terminology belongs to GitHub's native merge queue, not Mergify. Mergify validates .mergify.yml on push and typically rejects unknown top-level keys, which can disable the queue entirely until the config is corrected. If the intent is to serialize merges / run checks one at a time, set speculative_checks: 1 (and/or batch_size: 1) under the main queue rule instead.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (1 file)
Fix these issues in Kilo Cloud Reviewed by glm-5.2-short · Input: 8.1K · Output: 3.8K · Cached: 120.7K |
No description provided.