Reviews
The merge gate
The merge gate turns inline's review into a check on the pull request. Choose how strict it is, and GitHub will hold the merge until the findings it names are dealt with.
Choosing the mode is an admin task. Everyone else on the team sees the result in the merge box on their pull requests.
#What the gate does
inline posts a check named inline / review against the head of each pull request. The check names every finding still open, and in a blocking mode it fails while those findings stay open.
Some checks were not successful
A finding clears when its review thread is resolved on GitHub or a later push changes the flagged code.
The check keeps itself up to date. Resolve a thread or push a fix, and it re-runs on its own against the new state.
#The five modes
The modes run from posting nothing to holding the merge on any open finding. The middle three differ only in which severities count as blocking.
| Mode | What the check does |
|---|---|
| Off | No commit check is posted. |
| Report | Posts a check that always passes, carrying the open-findings tally so your team can see it without being held up. |
| Block high | Fails while high-severity findings are open. |
| Block med+ | Fails while medium or high severity findings are open. |
| Block all | Fails while any finding is open. Strictest. |
Report is a good place to start. It shows your team exactly what a blocking mode would catch, on real pull requests, before anyone is held up by it.
#How a finding clears
A finding clears when you resolve its review thread on GitHub, or when a later push changes the code that finding was raised against. Either one works, and both are things your team was going to do anyway.
Findings anchored to a review thread are the ones that can hold a merge, because a thread gives you somewhere to resolve. A finding with no thread still appears in the check summary, so you can read it and act on it.
#Sandbox tests in the gate
Where a repository runs sandbox tests, their result can feed the same check. Auto follows whatever you set the merge gate to. The other three decide on their own: Off, Report, or Block.
A test run still going keeps the check in progress instead of failing it. A failed test fails the gate. A run that could not start is reported as a note on the check instead.
#Where to set the mode
Review configuration
Defaults every repository inherits. Repos can override most settings on their own page or in .inline.yml unless a setting is locked under Enforced policy.
Defaults
Severity threshold
LowMediumHighReviews post as
inline botYour accountMerge gate
Default mode
OffReportBlock highBlock med+Block allCheck fails while high-severity findings are open — resolve the thread or push a fix to clear.
Sandbox tests
AutoOffReportBlockMonthly AI budget
Cap (USD)
No capSet the workspace default on Review config.
Under Merge gate, pick a Default mode. Every repository inherits what you pick.Override the default for a single repository from its own settings.
The same choices appear there, plus Default, which keeps that repository following the workspace. See Repository settings.
The merge gate is included with Pro. Plans and billing lists what each billing plan includes.