"What part of the code is broken? (perhaps 5 minutes tops?)" I expect this is where the git bisect advocacy comes from. Bisecting down to the commit that cause

"What part of the code is broken? (perhaps 5 minutes tops?)" I expect this is where the git bisect advocacy comes from. Bisecting down to the commit that caused the test to fail takes seconds. Then, you can start using the remaining process not unlike you mentioned to actually fix the bug. It helps remove that initial hunt for the problem. When you narrow the problem to a specific commit it becomes quite clear what is wrong immediately, not having to filter through the myriad of changes that may have come after. That is, at least, where I have found it to be most useful.