Reviews
Walkthroughs
A walkthrough reorganises a pull request into the order someone would explain it, so you start with what the change does and meet the files in an order that makes sense of it.
Anyone with the link can read a walkthrough, including people outside your workspace. Turning walkthroughs on for a repository is an admin task.
#What a walkthrough gives you
Notable changes
Cache keyed on head SHA · Added
Invalidation on force-push · Changed
Review payload shape · Structural
What changed
The review payload is now cached against the pull request head SHA, so a second pass over an unchanged head reuses it.
How it fits together
The cache sits between the diff fetch and triage, so a hit skips both.
Key changes
src/lib/review/cache.ts · src/lib/review/pipeline.ts
It opens on Recap, which explains the change in prose: what it does, how the pieces fit together, and which parts of it are worth your attention. Switch to Code for the diff itself, grouped into layers rather than listed by filename.
Notable changes down the left is inline's own reading order. Follow it top to bottom and you meet the change the way its author would explain it.
#Reading the code side
| Control | What it does |
|---|---|
| All files | Shows the whole diff rather than one layer. |
| Expand all, Collapse all | Opens or closes every file at once. |
| Hide moves | Drops files that only moved, so real changes stand out. |
Layers carry a Depends on note where one builds on another, so you can read them in an order that makes sense rather than guessing.
#Comment on it
Choose Comment and click anywhere on the recap to pin a note to that spot. Comments on the code side attach to a line, the way they do on GitHub.
You can also submit a full review from here, with Comment, Approve or Request changes, and it appears on the pull request as your review.
#Ask about the change
Ask inline opens a chat about this specific pull request. It has already read the change and the code around it, so a question like what should I review most carefully? gets an answer about your code.
#Share it outside the workspace
Every walkthrough has a link that works without a workspace account. Send it to a designer, a product manager, or a contractor who needs to see what changed without being given access to the repository.