Find that bad commit that broke your App with Git Bisect

Share this video with your friends

Send Tweet
Published 2 years ago
Updated 2 years ago

It always happens again. We have some weird bug in our codebase, hard to debug and just looking at the Git history doesn't help much. Git has a powerful command to help us: git bisect.

We have to simply identify a commit where the bug was not present, and the bad commit (usually the latest of the master or main branch). Then we invoke git bisect with both of them. The rest is just following along and answering questions. Let's see how that works.