Tracking down a kernel bug with git bisect
One thing that seems difficult with bisect are these series of steps:  1. "Hey... this bug didn't use to happen.  Where'd that get introduced?"
  2. OK, this unit test will tell me when the bug is fixed.
  3. Now lets automate bisect to tell me where this 
     test first failed even though I just wrote it.

How do you do that?  I think as long as you DON'T commit your unit test, bisect will carry over to every commit check.  But, you'll have to make sure you commit all your other changes or else they'll be carried around, too:  Conflict-city.Also, if you do commit your unit test (a "bad" habit of mine) I have no idea how I'm supposed to work with this.  I end up copying the unit test by hand to each commit it tries to test.In summary, it seems like bisect was built with manual testing in mind.  I know you can automate running a shell script, but I don't write my automated tests in shell script.EDIT: Keep in mind, not all projects are interpreted.  Some are compiled.