pastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 4 months agoCommitsh.itjust.worksimagemessage-square9linkfedilinkarrow-up130arrow-down10 cross-posted to: programmer_humor@programming.dev
arrow-up130arrow-down1imageCommitsh.itjust.workspastermil@sh.itjust.works to Programmer Humor@lemmy.ml · 4 months agomessage-square9linkfedilink cross-posted to: programmer_humor@programming.dev
minus-squareLemoineFairclough@sh.itjust.workslinkfedilinkEnglisharrow-up1·4 months agoDoesn’t git status tell you what to do? use “git add <file>…” to mark resolution use “git commit” to conclude merge I always use git status to check what is appropriate before doing anything else, since the right thing to do can sometimes be different, like after using git rebase when a break command was used vs when a squash command resulted in a conflict.
Doesn’t
git status
tell you what to do?I always use
git status
to check what is appropriate before doing anything else, since the right thing to do can sometimes be different, like after usinggit rebase
when abreak
command was used vs when asquash
command resulted in a conflict.