Skip to content

Post the conflict re-parent in plain git instead of uvx git-merge-onto - #68

Merged
Phlogistique merged 4 commits into
mainfrom
conflict-two-plain-merges
Nov 9, 2026
Merged

Phlogistique merged 4 commits into
mainfrom
conflict-two-plain-merges

Conversation

@Phlogistique

@Phlogistique Phlogistique commented Nov 6, 2026 •

Copy link
Copy Markdown
Collaborator

The conflict comment made people pull git-merge-onto. It now posts the same re-parent in plain git: merge a throwaway commit that has the target's content and both the target and the parent branch as parents. Git then merges from the same base that git-merge-onto forces, so the result is the same: one round of conflicts, rebase merges work, and the child's changes are kept.

The obvious plain-git recipe, git merge origin/<parent> then git merge origin/<target>, merges from an older base. It raises conflicts on lines the parent changed, and silently undoes some child changes, for example a deletion of a line the parent added.

Phlogistique and others added 4 commits November 6, 2026 18:00
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Phlogistique Phlogistique changed the title Post two plain merges in the conflict comment instead of git-merge-onto Post the conflict re-parent in plain git instead of uvx git-merge-onto Nov 9, 2026
@Phlogistique
Phlogistique marked this pull request as ready for review November 9, 2026 10:24
@Phlogistique
Phlogistique merged commit e2e87c7 into main Nov 9, 2026
3 checks passed
@github-actions
github-actions Bot deleted the conflict-two-plain-merges branch November 9, 2026 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant