Reviews
How a review works
Every pull request goes through the same steps. Knowing them tells you why one change comes back in seconds and another takes a couple of minutes.
Useful to anyone whose pull requests get reviewed, and to admins tuning how much inline says.
#What happens on every pull request
inline works out what changed.
On a second or later push it reads only what is new since the last review, so it is not re-reading work it has already covered.Triage decides how much attention the change deserves.
A fast pass reads the diff and calls it either substantive or trivial.A substantive change gets the full pass.
inline reads the surrounding code, opens the files a change touches, follows call sites, and searches the repository for anything that contradicts what it is about to say.The validation gate checks inline's own work.
Every finding has to survive a second look before anyone sees it. See Findings for what gets held back and why.inline posts what survived.
A summary comment, plus a comment on each line worth commenting on.
#The four verdicts
Reviews
Every pull request the agent has processed, newest first. Open one to see posted findings, suppressed findings, and cost.
| Pull request | Verdict | Findings | Cost | When |
|---|---|---|---|---|
| inline#482Cache review results per head SHA | Substantive | 3 | $•.•• | 2h ago |
| inline#481Bump tedious to 18.6.1 | Trivial | 0 | $•.•• | 5h ago |
| inline#479Rework the merge gate summary | Substantive | 1 | $•.•• | yesterday |
| Verdict | What it tells you |
|---|---|
| Substantive | The change earned the full pass, and inline read the code around it. |
| Trivial | Triage found nothing a deeper read would add. Typical for a dependency bump or a formatting change. |
| Skipped | Nothing left to review once your ignored paths and already-reviewed commits were taken out. |
| Incomplete | The pass stopped early. Your next push starts a fresh review of the pull request. |
Trivial and Skipped are both successful outcomes. They mean inline looked and had nothing to add, which is the answer you want on most small changes.
#What happens when you push again
Each push starts a new pass. inline reads what changed since the last one, which keeps a long-running pull request quick to review and stops it repeating points you have already dealt with.
After a run of those incremental passes, inline reads the whole pull request again from the top. That way a change built up over many commits is still seen as one piece of work rather than only as fragments.
#What inline reads besides the diff
During the full pass, inline pulls in what it already knows about your repository and your team:
| What it reads | Where it comes from |
|---|---|
| What it has learned about this codebase | Repo memory, built from past reviews |
| House rules you have taught it | Learnings |
| Expertise you have attached | Skills |
| What calls what | Code graph, where a repository has one |
| Your own instructions | Review config and In-repo config |