I can personally vouch for the awesomeness of 'git bisect', especially when combined with 'git rebase' to reconstruct trees minus troublesome commits.
Like many tools, I think git bisect's advantage comes from reducing the amount of thinking that you need to do to accomplish a task. Before git bisect I'd often stare at pieces of broken code or poke around in a debugger for hours on end. Now, ~1 hr or so with git bisect and friends, and the job is done...and I get to spend brain cycles thinking about something else.
7 comments
[ 1933 ms ] story [ 4231 ms ] threadScott Chacon touched on this in his SOR talk I think. There will be a vid up for it soon I think.
If you can write a shell script that returns 0 when the test passes and 1 when it doesn't, git bisect run will do the tedious part for you.
Like many tools, I think git bisect's advantage comes from reducing the amount of thinking that you need to do to accomplish a task. Before git bisect I'd often stare at pieces of broken code or poke around in a debugger for hours on end. Now, ~1 hr or so with git bisect and friends, and the job is done...and I get to spend brain cycles thinking about something else.