pastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 18 days agoCommitsh.itjust.worksexternal-linkmessage-square34fedilinkarrow-up10arrow-down10 cross-posted to: programmer_humor@programming.dev
arrow-up10arrow-down1external-linkCommitsh.itjust.workspastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 18 days agomessage-square34fedilink cross-posted to: programmer_humor@programming.dev
minus-squareLightfire228@pawb.sociallinkfedilinkarrow-up0·17 days agoI mean, you just need to look at the conflicting files, fix up the code, then stage those changes and pop a new commit There’s no “special” merge conflict resolution commit “type” As for fixing the code itself, I usually look at what changed between both versions, and then re-author the code such that both changes make “sense”
I mean, you just need to look at the conflicting files, fix up the code, then stage those changes and pop a new commit
There’s no “special” merge conflict resolution commit “type”
As for fixing the code itself, I usually look at what changed between both versions, and then re-author the code such that both changes make “sense”