Your CI was green last Friday. Today, the payments test is failing. Somewhere between Friday's merge and now, 47 commits landed on main. Which one broke it?
Most developers answer this the wrong way: they scroll through git log, check out suspicious commits one by one, and run the test manually. An hour later, they're still guessing.
There's a command built for this exact problem. It's called git bisect, and once you learn it, you'll never debug regressions the old way again.
How bisect works
git bisect is a binary search across your commit history. You tell Git two things:
