Update merge queue configuration

[kostua16]

No description provided.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[kilo-code-bot]

WARNING: merge_conditions uses a count-based check rather than re-checking the named checks.

queue_conditions explicitly requires check-success = Kilo Code Review and check-success = test-action, but merge_conditions only requires #check-success >= 2. This means the speculative merge commit could be merged as long as any two checks succeed, even if Kilo Code Review or test-action specifically fail on the speculative merge commit (e.g. due to a rename/typo in the check name, or an unrelated third check becoming green). For defense-in-depth, consider re-asserting the named checks in the merge conditions as well.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

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	7	merge_conditions uses count-based #check-success >= 2 instead of re-asserting the named checks required by queue_conditions, allowing speculative merge to proceed if any two checks pass even if Kilo Code Review or test-action fail.

Files Reviewed (1 file)

• .mergify.yml - 1 issue

Fix these issues in Kilo Cloud

---

_{Reviewed by glm-5.2-short · Input: 19K · Output: 3.2K · Cached: 160.4K}