Free for open source projects and schools. AI Council costs nothing for OSS maintainers and educational institutions. Apply →

Home / Docs / Review

Change review

Review checks a change against the project's conventions. It doesn't merge the merge request (MR) or change code. A person publishes findings as a separate step.

Reviewing a merge request

  1. Open Review. The Needs attention group lists merge requests waiting for review.
  2. Pick a merge request. The card shows its state, source and target branches, author and reviewer.
  3. Click Review.

The queue shows the 100 most recently updated merge requests. For the rest, and for branches without a merge request, use Review a branch in the screen header. For a merge request from a fork, enter pull/<number>.

Verdict and findings

A Blocked by review verdict explains exactly what stands in the way of merging. Findings at high and critical severity block. Merging isn't technically prevented: the decision stays with a person.

Finding fieldWhat it is
Severityhigh, medium, low, info
CategoryWhat was violated: Convention violation, Correctness and others
LocationFile and line
Explanation and How to fixAn explanation that names functions and files, and what exactly to change
Not an issueMarks a false positive: the finding stays in the list and no longer blocks merging

Auto-review

Click Auto-review off in the screen header and turn on Review new merge requests automatically. It applies to merge requests opened after you turn it on. In this mode, too, comments are published by a person.

The reviewer model and findings language are set in Settings → Code review. After you change the model or language, the next run rechecks all files.

Next: Tickets

Made on
Tilda