Skip to content

Update merge queue configuration - #10

Merged
kostua16 merged 1 commit into
mainfrom
mergify/kostua16/Ifda871f7b77654441fd46855c3bef22239fe0986
Jul 3, 2026
Merged

Update merge queue configuration#10
kostua16 merged 1 commit into
mainfrom
mergify/kostua16/Ifda871f7b77654441fd46855c3bef22239fe0986

Conversation

@kostua16

@kostua16 kostua16 commented Jul 3, 2026

Copy link
Copy Markdown
Owner

No description provided.

Signed-off-by: Konstantin <null>
@kostua16
kostua16 merged commit 483f2e4 into main Jul 3, 2026
3 of 4 checks passed
Comment thread .mergify.yml
- "#approved-reviews-by >= 1"
merge_conditions:
- "#check-success >= 2"
merge_queue:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@kilo-code-bot

kilo-code-bot Bot commented Jul 3, 2026

Copy link
Copy Markdown

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 1
SUGGESTION 0
Issue Details (click to expand)

WARNING

File Line Issue
.mergify.yml 9 merge_queue: / max_parallel_checks is not a valid Mergify config key; parallelism is controlled via speculative_checks inside queue_rules
Files Reviewed (1 file)
  • .mergify.yml - 1 issue

Fix these issues in Kilo Cloud


Reviewed by glm-5.2-short · Input: 8.1K · Output: 3.8K · Cached: 120.7K

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant