Try this Git developer challenge: a bug appeared somewhere in the last 500 commits, and you have a test that detects it. What’s the shortest path to find the exact commit where it was introduced? Share your answer in the comments.
VIDEO
You don’t need to check commits one by one. Git has a built-in tool for reducing the search space.
Use git bisect.
Why: git bisect uses binary search to narrow down the first bad commit. After that, you test each commit Git selects and mark it good or bad until Git identifies the exact one.
Why: git bisect uses binary search to narrow down the first bad commit. After that, you test each commit Git selects and mark it good or bad until Git identifies the exact one.
Generated by Thread Navigator
Press ⌘ + S to quick-export