STACKED CODE REVIEW · BUILT FOR GIT & JUJUTSU
Rewrite history. Keep the review.
A pull request gets rewritten a dozen times before it lands. Revset shows each reviewer only what changed since they last looked — anywhere in the stack, with their comments still on it. Git or Jujutsu.
Four things you notice on the first re-review.
Diffed against your last read
Revset stores the revision you last opened and sets the comparator from there. You never have to remember where you stopped.
Threads that survive a rewrite
Comments anchor to content, not to a commit sha. Amend, rebase, force push — the thread stays on the line it was written about.
Reviewed markers, per revision
Mark a file reviewed and it stays marked until that file actually changes. When it does, only that file comes back to you.
The stack knows the order
Merge the bottom and everything above rebases and keeps its reviews. Revset re-points the pull requests without asking you to.
Five questions that come up before you switch.
Every one of them is really the same question: what happens to a review when the commits underneath it stop existing.
GitHub ties review comments to specific commits. Rewriting history — amending, rebasing, force pushing, all routine in a Jujutsu (jj) workflow — replaces those commits, so comments get marked outdated and reviewers lose track of what actually changed. Revset keeps comments and review context attached across revisions.
SEE IT ON YOUR OWN STACK
Rewrite it again.We'll keep up.
OPEN SOURCE AT LAUNCH · NO CARD · NO SALES SEQUENCE