Revset Keeps Code Review Intact Through Force Pushes

Field notes

The page models review as a sequence of revisions rather than a single immutable commit snapshot. Its example follows five revisions and shows reviewers comparing later work with the point they last opened, while comments remain attached to code content and file-review markers return only when a file changes. The displayed stack includes six numbered pull requests and a seven-file change set, giving the product’s promise a concrete operational shape rather than leaving it at the level of workflow slogans.