Verdicts and severity

A Vetoo review has two layers: the findings on the change, and one verdict on the request.

Findings and severity

Each finding appears inline, on the line it refers to. The finding carries a severity and a suggested fix. The severity tells you how to prioritize the finding. You must handle a blocking finding before you merge. A note is a smaller item, such as a readability suggestion. A note does not block the merge.

Where Vetoo can suggest a fix, the finding does more than name the problem. Vetoo puts the suggested fix in the comment, which saves the author time.

The verdict

The request also gets one verdict.

• Approve. No blocking findings. Ready to merge as far as Vetoo can tell.
• Comment. Feedback worth reading, with no blocking findings.
• Request changes. At least one blocking finding to resolve first.

A repository on the CHECK_ONLY review mode skips this layer. Vetoo still reviews the change, but it posts a status check instead of a verdict. On the other three modes, the review mode sets which verdict Vetoo can post. A repository on COMMENT never requests changes, even for a blocking finding. A repository on APPROVE can approve the request. Vetoo posts a comment instead when the change is large, or when Vetoo's confidence is not high.

Tutorial comment

Vetoo adds a short collapsible walkthrough beside each posted review, one walkthrough per request. The walkthrough explains how to reply, how to vote, and how to start another review. An admin can disable the walkthrough for the workspace in review preferences on the Repositories page.

Where reviews appear

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. Filter the list by a date range, or by a preset for the last week, month, or quarter. Skipped reviews also appear, and Vetoo marks them as skipped rather than giving them a verdict.