My favorite part of `git bisect` is `run`: give it a script that'll exit with 0 for a good commit and non-0 for a bad commit, and it'll do it all for you!

Personal gripe: I always, always, forget to `git bisect reset`.

A friend blew my mind with this a while ago when I was trying to track down a commit which broke something. This short guide he wrote gives step by step instructions for using it with your tests: https://gist.github.com/jordelver/5998870

I did not know about that.

Article from lwn: http://lwn.net/Articles/317154/

thanks for the tip!

Solution: Automate it https://github.com/grosser/git-autobisect

Hm, how does it decide how far back to start?

It defaults to looking through the last 1000 commits, as it's automatic it doesn't really matter if it isn't optimal.

Just means you might be grabbing more coffee than you were expecting, especially if your test takes some time.

patio11 has a great story about how he learned of it, via Patrick Collison:

http://www.kalzumeus.com/2012/08/06/stripe-and-ab-testing-ma...

Wow, kudos to Patrick.