magic-merge-commit

Create Magic Merge Commit

Have you ever created a branch based on another branch? Then that other branch got squash-merged into main. Now your pull request, which was based on that branch, can’t merge cleanly because Git sees your old commit as conflicting with the squashed commit in main?

This tool generates a special merge commit that links your branch to the squashed history in main, eliminating the conflict and letting you merge main without trouble.

Execute the tool with following command:

jbang do@koppor/magic-merge-commit <pr-number>

<pr-number> is the number of the pull request which was squashed-merged into main. You need to be on the branch which is based on the pull request indicated by <pr-number>.

Installation

To have jbang working, you need to install it. Find information at the jbang page.

If you don't want to install jbang, this repository already ships gg.cmd in its root. Execute as follows:

• Linux/macOS: sh ./gg.cmd jbang do@koppor/magic-merge-commit <pr-number>
• Windows: .\gg.cmd jbang do@koppor/magic-merge-commit <pr-number>

Use as a Claude Code skill

This repository is also a Claude Code plugin. Install it so Claude runs the tool for you when it detects a squash-merge conflict:

/plugin marketplace add koppor/magic-merge-commit
/plugin install magic-merge-commit@magic-merge-commit

The skill still requires jbang (or gg.cmd) and a GITHUB_TOKEN environment variable on your machine — it tells Claude when and how to invoke the tool, it does not bundle the tool itself.

Step-by-step description of the scenario

1. First pull request is created

The pull request starts with one commit.

2. Second pull request is created

Another improvement is needed. It should be reviewed separate pull request, but needs the first pull reuqest.

Therefore, a new branch is created and a commit is added to it. Finally, a second pull request is created, based on the first one, which is still opened.

3. First pull request is merged in to main

4. main branch has its own commit

The conflicting change in main.

5. Conflict Arises with the main branch

The second commit in the pull request conflicts with the main branch, which has its own commit.

6. Conflicting state visualized with gitk

The first pull request was added as commit to the main branch. There is no git merge commit and there is no git connect with the pull request. The only indicator is #1 in the commit message.

7. The magic commit is created

This tool creates a new commit that has both main and pr-last-commit as parents. This commit "magically" resolves the conflict by wiring the two branches together.

8. Merge without conflicts

This "magic" merge commit now merges cleanly.

More information

• The tool gh-cherry-pick is a GitHub CLI extension allowing to gh cherry-pick -pr <pr-number> -onto <target_banch> allows to cherry-pick PRs into unrelated branches.
• gitk was used to visualize the commits. Learn more about it at lostechies.
• The scenario is available at squash-merge-demo.
• Background is available at a blog post.