Merge gate
A required check that keeps a pull request from merging until its review findings are dealt with, so a coding agent knows when it is done.
CodePanel's merge gate is the CodePanel commit status. It fails while any finding at or above the repository's gate level is unanswered, passes once every one is fixed, dismissed or decided, and blocks a merge only when the repository makes it a required check.
In an agent review loop
The gate is how a coding agent knows it has finished. On a repository with CodePanel as a required check and auto-merge on, the loop runs like this:
- The agent opens the pull request and turns on auto-merge.
- The review posts two warnings, F1 and F2. The status fails, naming both.
- The agent fixes F1, disputes F2 with a
file:line, and rates both with/feedback. - The orchestrator withdraws F2. The status turns green within seconds.
- GitHub merges the pull request with no person involved.
If the agent's session ends at step 3, the pull request waits on the gate rather than merging with an open finding.
Gate levels
The level sets which severities must be answered: critical, warning (the default), all, or off. A failed review never blocks on its own, so an outage on the reviewer's side does not hold a merge. See merge gate for the status rules and how to require it.