Reference / Merge policy
Your policy.
The judge applies it.
By default, separate review and QA must pass before the judge merges. You configure the review policy, CI gate and whether the project permits auto-merge.
Read a merge recordDefault review policy
Try the verdicts
Assumes auto-merge is enabled and the default review and CI gates are in use.
Under the default policy, review and QA must pass on the current revision. Failed checks return findings to the coder.
Judge decision
Await QA
The reviewer passed. The judge waits for a QA verdict.
Authority by role
Separate work.
Separate verdicts.
- Coder
- Builds and updates the change. Review, QA and merge permissions belong to other roles.
- Reviewer
- Checks the diff against the task. Records a pass or actionable findings for the coder.
- QA
- Runs tests against the acceptance criteria and records a separate verdict tied to the checked commit.
- Judge
- Applies the configured review and CI gates, checks the current revision and mergeability, and respects project auto-merge settings.
Configuration
Choose the gate.
- Default checks
judge_review_gate=passpassrequires passing review and QA.judge_ci_gate=prwaits for green PR checks.- CI-led review
judge_review_gate=greenallows missing PASS verdicts when CI is green on the current head and no current review or QA verdict is FAIL. CI remains required in this mode.- Optional CI gate
judge_ci_gate=noneskips the judge’s PR-check gate under the default review policy. It retains verdict and mergeability checks. Read the configuration guide before changing this policy.- Human handoff
- Register a project with
--no-auto-mergeto make the judge stop before merging.
Fictional demo / G-001
A pricing table
takes two tries.
The reviewer rejects the first attempt on task T-0003. On the revised commit, review and QA both pass, CI is green and the judge merges pull request #102. The task preserves both attempts.
Read the task history