pastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 20 hours agoCommitsh.itjust.worksimagemessage-square31fedilinkarrow-up1646arrow-down16 cross-posted to: programmer_humor@programming.dev
arrow-up1640arrow-down1imageCommitsh.itjust.workspastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 20 hours agomessage-square31fedilink cross-posted to: programmer_humor@programming.dev
minus-squareLightfire228linkfedilinkarrow-up1arrow-down1·4 hours 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”