SagXD@lemm.ee to Programmer Humor@programming.dev · 9 months agoMy Git Knowledgelemm.eeimagemessage-square178fedilinkarrow-up11.12Karrow-down125
arrow-up11.1Karrow-down1imageMy Git Knowledgelemm.eeSagXD@lemm.ee to Programmer Humor@programming.dev · 9 months agomessage-square178fedilink
minus-squaredarkpanda@lemmy.calinkfedilinkarrow-up12·9 months agoLearn to use git bisect. If you have unit tests, which of course you should, it can save you so much time finding weird breakages.
minus-squarexthexder@l.sw0.comlinkfedilinkarrow-up11arrow-down1·9 months agoWith automated CI, I’ve had very few times where bisect is useful. Either the bug was introduced 1-2 commits ago, or it’s always been there and the exact commit is irrelevant to the solution, since you just fix it forward.
Learn to use
git bisect. If you have unit tests, which of course you should, it can save you so much time finding weird breakages.With automated CI, I’ve had very few times where bisect is useful. Either the bug was introduced 1-2 commits ago, or it’s always been there and the exact commit is irrelevant to the solution, since you just fix it forward.