Guide: stacked PRs

Create, review, and land a chain of dependent PRs with ADE lanes.

Use stacked PRs when one feature is too large for a single review but each slice depends on the previous slice.

1. Create the base lane

Create a lane from main for the first slice of work. Commit the foundation there.

2. Create child lanes

Select the base lane and create a child lane for the next slice. Repeat only as needed.

main
  feature-auth-models
    feature-auth-ui
      feature-auth-tests

3. Open PRs

Open PRs from the bottom of the stack upward:

• Base lane targets main.
• First child targets the base lane branch.
• Next child targets the first child branch.

ADE keeps this relationship visible in Lanes, Graph, and PRs.

4. Review in order

Review the base PR first. Child PRs will be easier to understand once the parent is approved.

5. Land the stack

1. Merge the base PR

   Land the first PR into main.

2. Update the child

   Rebase or retarget the next PR so it now builds on main.

3. Repeat

   Continue up the stack until all slices are merged.

Tips

• Keep each PR small enough to review independently.
• Avoid deep stacks unless the dependency is real.
• Use Graph to see the chain.
• Run tests again after rebasing a child.
• If a child becomes independent, split it into a sibling lane.

Stacked lanes

Understand the lane model.

Pull requests

Review and merge from ADE.