Review modes
The four review modes, how the org default and per-repo overrides work, and when a mode needs extra permission.
The review mode sets how far Vetoo takes a review after it reads the change. The modes range from a status check only, to a verdict on the request itself. Auto-review is a separate setting, and it decides whether Vetoo reviews a repository without a prompt. See Managing repositories.
The four modes
| Mode | Inline comments | Acts on the request |
|---|---|---|
CHECK_ONLY | No | Posts a status only |
COMMENT | Yes | No, comments only |
REQUEST_CHANGES | Yes | Requests changes for a blocking finding |
APPROVE | Yes | Approves when nothing blocks |
CHECK_ONLY runs the review but posts nothing inline. COMMENT posts the full findings and leaves the request's state unchanged. REQUEST_CHANGES and APPROVE also act on the request itself.
Default and overrides
Set one default mode for the workspace. Every repository follows that default until you override it. To override the mode, open the repository on the Repositories page. Then choose another mode. A repository you are still testing can use COMMENT while the rest of the workspace uses REQUEST_CHANGES.
When a mode needs permission
On GitHub, three modes write to the pull request: COMMENT, REQUEST_CHANGES, and APPROVE. Each of them needs one more app permission. Until you grant that permission, CHECK_ONLY is the only mode available, and Vetoo disables the other three. GitLab restricts no mode this way, so all four modes work as soon as the connection is live.
A change to a repository's mode takes effect on its next review. It does not change reviews that Vetoo already posted.