Verify the change, and what depends on it, before human review.
Veridu reviews every push to a draft pull request, so the author works through the findings first and the human reviewer starts from a clear handoff.
- 1Open a draft pull request. With "Review before a human" turned on for the repository, Veridu reviews the draft on every push.
- 2Fix or dismiss findings. Each finding has a label such as F1. Fix it and push again, or dismiss it with a reason: comment /veridu dismiss F1 <reason>, or use Dismiss on the review page. Later reviews re-check what is still open.
- 3Reach a clear gate. Nothing blocks, the review saw all of the code and every reviewer answered, and no finding at the repository's display level (medium by default) or above is left open.
- 4Hand off to a human. Veridu adds "Ready for human review" to the PR comment. The author marks the draft ready for review; if the repository uses code owners, GitHub then requests them.
- How big the change is
- Which code owners the changed files belong to
- How many places outside the change use the changed code
- How many reviews ran, and how many earlier findings are no longer reported
- How many findings were dismissed (each reason is listed in the comment)
- What is left for human judgment: findings below the display level, and the ones the reviewers disputed
No open findings at medium or above. This is not an approval: it says what Veridu checked, so a reviewer can start from here.
- Change: 1 file, +34/−0
- Used outside the change: no references found
- Rounds: 3 reviews · 2 earlier findings no longer reported
- Left for human judgment: 2 findings below medium
Ready to be marked for review. If the repo uses code owners, GitHub then requests them.
"Ready for human review" is not an approval. The human reviewer decides.
Does Veridu approve the pull request?
No. "Ready for human review" says that nothing at your display level or above is left open in what Veridu checked. The human reviewer decides, and required checks stay yours.
Does Veridu mark the draft ready or request reviewers?
No. The author marks it ready. If the repository uses code owners, GitHub requests them at that point, as it always does.
What if a finding is wrong?
Dismiss it with a reason. The dismissal records who dismissed it and why, the reason is listed in the PR comment, and /veridu undismiss F1 brings it back.
Is every push reviewed in full?
The first review of a pull request is. Later pushes can be reviewed against the last review: the new commits, with what was still open checked again. When that would leave nothing open, Veridu reviews the whole change before showing the handoff.
What does it cost?
Every push to a draft is a review, so it uses more of your reviews per pull request than reviewing once when the pull request is ready. Plans and allowances are on the pricing page.
What do I need?
The Veridu GitHub App on the repository. Then turn on "Review before a human" in that repository's settings on veridu.io. It is off until you do.
Connect the repository with the Veridu GitHub App, then turn on Review before a human in its settings. Every push to a draft is a review, so it uses more of your reviews per pull request. See pricing.