Once your stacked pull requests are approved, mrge offers a dedicated UI (mrge.io) for merging them in the correct order—no guesswork or manual rebasing required. Each dependent branch is merged in sequence, preventing conflicts and ensuring a clean commit history.

You can merge in GitHub’s interface if you prefer. However, the mrge UI displays an at-a-glance view of your stack, making it easy to see dependencies, merge partially, or skip certain branches if needed.

​
Why merge in mrge?

  • Automatic Ordering: Child branches can’t merge until their parent is merged, so you never accidentally merge a downstream branch first.

  • Clear Visibility: See which branches are ready to merge and which are still awaiting review or CI checks.

  • Partial Merges: Land just the bottom few branches if needed, and mrge will restack the remaining branches on top of the newly updated trunk.

​
1. Open your repository in mrge

1

Sign in

Go to mrge.io and sign in with your GitHub account.

2

Locate your repo

From your dashboard, select the repository that contains your stacked PRs.

3

Choose your stack

mrge automatically detects your open PRs and displays them in a stack view.

​
2. Review branches

Before merging, you might want to:

  • Check diffs: Click each branch to see its changes, commits, and any review comments.

  • Update the code: If there’s feedback or a last-minute fix, go back to your local setup, edit, and push changes (Keep your stack updated). mrge will reflect those updates automatically.

​
3. Merge in sequence

1

Merge the bottom branch

Click Merge on the lowest branch in the stack (the “parent”). mrge merges it and updates the trunk automatically.

2

Continue up the stack

Move to the next branch that depends on the one you just merged, and click Merge again. Repeat until you reach the top.

Partial merges: If you only want to merge the first few branches for now, that’s totally fine—mrge restacks the remaining branches on top of the new trunk.

​
4. Sync locally

Once you’ve merged some or all of your branches, update your local environment:

mg sync

This ensures your local stack is up-to-date and merges are reflected. Merged branches disappear from mg list (unless they still have children that aren’t merged yet).

​
Done!

Your stacked PRs are successfully merged. Time to celebrate—or start another stack!

  • More merging questions? Head to our FAQ.

  • Got new features? Rinse and repeat with mg branch or mg branch -t to automatically create the new branch from trunk.

Thanks for using mrge!

Was this page helpful?