Code review
Re-reviews and summaries
When a pull request changes, Codebot reviews what’s new, closes what was fixed, and keeps one summary up to date.
Reviewing new commits
When commits are pushed to a pull request Codebot already reviewed, the next review focuses on what changed since the last reviewed commit. It still has the whole pull request and repository for context.
After a force push, or when someone asks with @trycodebot review, Codebot reviews the whole pull request again.
Earlier findings
Every review sees Codebot’s earlier comment threads on the pull request, open and resolved, with your replies. That lets it:
- Resolve fixed findings. When a new commit fixes something Codebot flagged, it replies on the thread saying how it was fixed and resolves it.
- Avoid repeats. A finding that matches an open Codebot thread isn’t posted again.
- Take your replies into account. If you explain on a thread why something is fine, the reviewer reads it.
Codebot only resolves threads it started. Threads from people are never touched.
The summary comment
Each pull request gets one summary comment from Codebot, headed Codebot review, that it edits after every review instead of posting a new one. It shows:
- the verdict and the commit that was reviewed;
- how many earlier findings were resolved, and how many are still open;
- the reviewer’s overview of the change, and anything it couldn’t review.
The review itself links to the summary. A review that only comments and has no inline findings isn’t posted at all: the summary already says everything.