Skip to content

Post two plain merges in the conflict comment instead of git-merge-onto - #68

Draft
Phlogistique wants to merge 1 commit into
mainfrom
conflict-two-plain-merges
Draft

Phlogistique wants to merge 1 commit into
mainfrom
conflict-two-plain-merges

Conversation

@Phlogistique

Copy link
Copy Markdown
Collaborator

The conflict comment made people pull git-merge-onto to resolve a conflict. It now asks for two plain merges: the parent branch, then the target. The action itself still uses the vendored copy when there is no conflict.

The cost is a second merge commit, and if the child edited its parent's lines, the same conflict comes up in both merges.

Known limit: if the child deleted a line its parent added, git merge origin/<target> brings the line back without a conflict. git-merge-onto kept it deleted. I reproduced this locally; it has not been seen in production.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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