mergify: remove coderabbit comment requirement

[ktdreyer]

CodeRabbit does not leave a review if there are no actionable comments. When Mergify does not see the CodeRabbit review, it will not merge the PR, even if the PR meets all the other criteria (successful human review + passing tests).

The purpose of adding coderabbit to the Mergify criteria is to provide a natural quality governer: to ensure that humans read the reviews. Turns out CodeRabbit is useful enough that we don't need to enforce this with Mergify, and tweaking it further is not worth optimizing.

Fixes: #940

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 16be7c77-434f-49a4-97c4-54269379aff2

📥 Commits

Reviewing files that changed from the base of the PR and between 37e6fad and 1be956e.

📒 Files selected for processing (1)

• .mergify.yml

💤 Files with no reviewable changes (1)

• .mergify.yml

---

Walkthrough

Removes the commented-reviews-by=coderabbitai[bot] condition from the queue_conditions of the large-pr and default queues in .mergify.yml, dropping the bot review/comment requirement while leaving other checks unchanged.

Changes

Cohort / File(s)	Summary
Mergify configuration .mergify.yml	Deleted commented-reviews-by=coderabbitai[bot] from queue_rules for large-pr and default, removing the bot review gating condition.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: removing the CodeRabbit comment requirement from Mergify configuration.
Description check	✅ Passed	The description provides relevant context about the change, explaining why CodeRabbit was originally added to Mergify and why it is no longer necessary.
Linked Issues check	✅ Passed	The PR successfully addresses the objective in linked issue #940 by removing the commented-reviews-by=coderabbitai[bot] condition from .mergify.yml.
Out of Scope Changes check	✅ Passed	All changes are directly related to the stated objective of removing the CodeRabbit requirement from Mergify configuration with no extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kdreyer/mergify-coderabbit

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can use your project's `golangci-lint` configuration to improve the quality of Go code reviews.

Add a configuration file to your project to customize how CodeRabbit runs golangci-lint.

[jeremyeder]

Hey, something to think about - we will need to find a type of PR that we are ok auto merging. Are there stats collected from mergify that we could learn from?

…

-- Jeremy Eder (he/him/his)

On Tue, Mar 17, 2026, 10:39 Ken Dreyer ***@***.***> wrote: CodeRabbit does not leave a review if there are no actionable comments. When Mergify does not see the CodeRabbit review, it will not merge the PR, even if the PR meets all the other criteria (successful human review + passing tests). The purpose of adding coderabbit to the Mergify criteria is to provide a natural quality governer: to ensure that humans read the reviews. Turns out CodeRabbit is useful enough that we don't need to enforce this with Mergify, and tweaking it further is not worth optimizing. Fixes: #940 <#940> ------------------------------ You can view, comment on, or merge this pull request online at: #941 Commit Summary - 37e6fad <37e6fad> mergify: remove coderabbit comment requirement File Changes (1 file <https://github.com/ambient-code/platform/pull/941/files>) - *M* .mergify.yml <https://github.com/ambient-code/platform/pull/941/files#diff-6a30e47dd51449847422017b16878889b848f6602ac56d5a2e67ce8a19afade2> (2) Patch Links: - https://github.com/ambient-code/platform/pull/941.patch - https://github.com/ambient-code/platform/pull/941.diff — Reply to this email directly, view it on GitHub <#941>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOUVGHX7KSPT355CUDKPBL4RGEVNAVCNFSM6AAAAACWU6K3IGVHI2DSMVQWIX3LMV43ASLTON2WKOZUGA4TAMJQGIZTCMI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mprpic]

It's too bad there isn't a generic commented-on-by that counts any comment, not just review comments.

[ktdreyer]

@Mergifyio queue

[mergify]

Merge Queue Status

• 🟠 Waiting for queue conditions
• ⏳ Enter queue
• ⏳ Run checks
• ⏳ Merge

Required conditions to enter a queue

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -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 >= 1 [🛡 GitHub repository ruleset rule protect-main]
    • #approved-reviews-by>=1
    • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule protect-main]
    • #changes-requested-reviews-by=0
    • check-success=End-to-End Tests
    • check-success=test-local-dev-simulation
    • check-success=validate-manifests
  • all of [📌 queue conditions of queue large-pr]:
    • #approved-reviews-by>=2
    • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule protect-main]
    • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule protect-main]
    • #changes-requested-reviews-by=0
    • check-success=End-to-End Tests
    • check-success=test-local-dev-simulation
    • check-success=validate-manifests