2 ms·
Honestly? Almost never. I guess more traditional methods of debugging code are good enough to identify where problematic issues are, and git blame is enough to
by yen223 5y ago
Honestly? Almost never.
I guess more traditional methods of debugging code are good enough to identify where problematic issues are, and git blame is enough to identify the offending commit.
- dmlittle 5y agoHistorically I've used bisect on codebases I wasn't familiar with knew there was a regression I was trying to fix. If you can automate your regression testing with a script git bisect is really powerful and will save you _a lot of time_. Although if it's easy to test given the logarithmic nature of bisect maybe writing the script might not be worth the time.