Skip to content

Git Bisect and Why it is Amazing

Updated: at 04:16 PM

If you need to pinpoint a certain change among many git commits, try the git bisect command

Had a client email me recently, mildly concerned, as an update to WP eCommerce broken his search layout. I told him that I couldn’t think of anything between the latest version and the prior version that would have caused any such thing, but I’d be more than happy to check it out.

I dug in and in fact, we had broken it. I didn’t recall any changes in the 913 commits between the two changes.

With nothing obvious, and 913 commits between release - what was a developer to do? Enter, git bisect.

Read more from the source: Zao