
A pull request's Overview in Change Stack, in an example repository: its layers in the rail, a summary of what changed, and what blocks the merge. The Summary's chips also count the merge conflict, rated Critical.
Review a pull request
Every CodeRabbit review comment carries a Review Change Stack â button above the walkthrough. You can also open Change Stack from or from a link a teammate shares.
The "Review Change Stack â" button in a CodeRabbit review comment
Open the overview
Choose how to move through the change
Read the changes and findings
Ask for context when you need it
Finish the review
How a change is structured
Change Stack builds the pull request into a stack of numbered layers. A layer is a checkpoint in the change: a coherent step, with the files and review context that belong to it. Inside a layer are the changed files, and inside those are ranges: spans of source lines that carry a summary, a finding, or a review anchor. The range is the level that makes the rest work. Because summaries and findings attach to source spans rather than to whole files, Change Stack can put a summary beside the lines it describes, jump from a finding on a dependency graph to the code that produced it, and tell you whether that finding is still open three pushes later.
One layer of the same example pull request, with a critical finding anchored to the lines it describes