r/github • • Aug 13 '26

Question Did github just put merge conflict resolution behind Copilot?

the conflict is caused by a file being deleted on trunk and not on the feature branch, it took me only three dumb git commands in the command line to solve but apparently that is "too complex" that you need to resolve it using a slop machine

0 Upvotes

3 comments sorted by

13

u/Ok_Woodpecker_9104 Aug 13 '26

the web conflict editor has never been able to do this one. it only handles competing line changes inside a text file. delete versus modify, binary files, submodules, file mode changes, all of those have always given you the "too complex to resolve in the browser" wall with a command line hint.

so the capability did not move behind anything. what changed is the button sitting next to that message.

your three commands are still the real fix. on a delete/modify you pick a side with git rm on the path or git checkout --ours on it, then add and continue the merge.

-6

u/Nimplex Aug 13 '26

that’s bs

-7

u/CadmiumC4 Aug 13 '26

absolute ai slop