How a review happens
Follow each step, from the moment a request opens to the final verdict.
A review runs from start to finish without manual steps. How the review starts depends on the repository's settings.
You open a request
Open a pull request or a merge request. If you enabled auto-review for the repository, Vetoo starts the review at once. If you disabled auto-review, comment @vetoo-review review this to start the review. Vetoo skips a draft request until you mark it ready.
Vetoo reviews the change
The panel reads your change together with the surrounding code. It also reads context from connected tools, such as Notion or an issue tracker. See Integrations. Vetoo then posts its findings as comments on the request.
You read the comments
Each finding appears inline, on the line it refers to. The finding carries a severity and a suggested fix. Blocking findings carry no label. Vetoo labels every other severity, so you can tell the two apart at a glance. Vetoo also posts one verdict on the request: approve, comment, or request changes. The repository's review mode sets which verdicts Vetoo can post.
You reply, vote, or start another review
To ask a question or to push back, reply in the thread and mention @vetoo-review. Vetoo answers. Vote a finding down, and Vetoo does not raise that kind of finding in later reviews of the repository. To review new commits, comment @vetoo-review review this.
The verdict tracks the code
Each new review updates the verdict to match the current code. When you resolve every blocking finding, the verdict changes with them.
Every completed review appears on the Reviews page in the app. Each row shows the repository, the request number, the result, the time it ran, and the credits used. See Verdicts and severity.