Create a stack

​

Interactive Demo

Learn about stacked PRs interactively in your CLI:

mg demo

Stacks allow you to break a big feature into multiple dependent branches, each with its own PR. This approach makes it easier to review smaller, self-contained changes instead of dealing with one massive pull request.

​

1. Start from your trunk

Begin by checking out your trunk branch (often main or master):

mg checkout main

​

2. First branch

Make your first set of changes:

mg branch part_a
echo "console.log('Part A')" > partA.js
mg add partA.js
mg commit -m "feat: part A"

You can open a pull request immediately by pushing:

mg push

​

3. Second branch on top

Let’s build on that first branch:

mg branch part_b
echo "console.log('Part B')" > partB.js
mg add partB.js
mg commit -m "feat: part B"

Now, if you run:

mg list

You’ll see a short tree:

main
 └─ feat_part_A
    └─ feat_part_B

Each of these branches can become its own PR.

​

4. Push & review your branches

mg push --all

This command updates (or creates) your pull requests on Mrge (and GitHub). Each branch is a smaller PR, but together, they form one cohesive feature. Your team can review them in sequence or parallel, merging them once approved.

​

5. Keep moving

• Check out the next branch in the stack: mg next

• Check out the previous branch in the stack: mg prev

• Visualize again: mg list

Add as many branches as you need for each logical slice of your feature.

​

Best Practices

• One logical change per branch: Keep each branch focused on a single feature or sub-feature.

• Name branches descriptively: It’s easier to see what each PR does when reading the branch list.

• Push frequently: Ensures your teammates can see your ongoing work and provide feedback early.

​

Next steps

• Keep your stack updated: Sync from main if teammates add new commits.

• Merge your stack in Mrge: Once each PR is ready, merge them in the right order via the Mrge UI.