Stacked lanes

Use stacked lanes when a large change is easier to review as several dependent PRs.

A stack is a chain of lanes. Each child lane is based on the lane above it instead of directly on main.

main
  auth-models
    auth-ui
      auth-tests

Each lane can become its own PR. Reviewers see small diffs instead of one giant branch.

Create a stack

1. Create the base lane

   Start the first slice from main or your default branch.

2. Create a child lane

   Select the parent lane and choose New child lane.

3. Repeat only when needed

   Keep stacks shallow. Two or three levels are much easier to review than six.

Work with a stack

• Open PRs from bottom to top.
• Child PRs target their parent branch.
• Merge the base PR first.
• Rebase or retarget child PRs after the parent lands.
• Use Graph when the stack gets hard to picture.

When not to stack

Do not stack unrelated work. If two tasks can merge independently, use two sibling lanes instead.

Stacked PR guide

Follow the end-to-end review flow.

Workspace graph

Visualize stack relationships.