git bisect; finding exact commits of bugs

[Graham Percival]

If it doesn't exist already, is it worth writing something for the
CG about using git bisect to find the exact commit where a
regression was introduced?

If it does exist, would it be worth trying to convince a frog or
two to spend time doing this?  I heartily admit that it's not
glamorous work, but if any regression issues could have the commit
identified, I imagine it would be one less task for whoever's
working on a patch for said regression.

Cheers,
- Graham