Sure; if you never write code that contains bugs that your unit tests don't catch, then "git bisect" is probably useless to you. As for the rest of us mere mor

Sure; if you never write code that contains bugs that your unit tests don't catch, then "git bisect" is probably useless to you. As for the rest of us mere mortals, we sometimes write code that has bugs without discovering those bugs right away. In a complex system, it might not be easy to observe an incorrect behavior and immediately deduce the root cause. "git bisect" allows you to retroactively track down the commit that introduced a behavior change, even if it was something you didn't originally think to test for.