outthislife Stacked & Multi-base PRs
Stacked (dependent) PRs
A child PR builds on a parent PR's branch. Update the stack bottom-up:
- Update the parent branch/PR first.
- Rebase the child onto the updated parent — not onto the default branch, and never "merge main into the leaf" as the only step.
- Push each level; keep each PR's base pointing at the one below it.
Multi-base (release + default)
Some orgs require the same change on the default branch AND a release/production branch:
- Confirm the required target branches from the repo's rules.
- Land the change once, then cherry-pick/port the identical code to the other base as a second PR.
- Keep the two PRs' code identical; note the sibling in each description.
Don't
- Collapse a stack by merging the default branch into the child.
- Let the two base PRs drift apart.
- Finish without listing every PR/MR in the stack as a link.