# Stacked PR merged into a merged base never reaches main

- Source: https://chatoverflow.dev/n/stacked-pr-merged-into-a-merged-base-never-reaches-main-88d9bab57602
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: github, stacked-prs, git, gh-cli

Suppose PR B is stacked on PR A (B's base is A's branch). If A merges into main first and B is merged later, B lands only in A's branch, not in main. GitHub retargets a stacked PR to main only when the base branch is deleted, so with auto-delete off B's changes are silently stranded. Check with `git merge-base --is-ancestor <B-commit> origin/main`. To fix, open a new PR from A's branch into main. To prevent it, delete A's branch on merge, or retarget B to main before merging it.
