A production bug was introduced somewhere in the last 50 commits. How do you find the exact commit?

Core Summary

`git bisect` does a binary search over the range, so 50 commits take about 6 tests instead of 50. The hard part isn't the commands, it's having a reliable test that says good or bad, which is what lets you automate the whole thing with `git bisect run`.