Find that bad commit that broke your App with Git Bisect
InstructorJuri Strumpflohner
Published 3 years ago
Updated 3 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.
egghead
~ 29 minutes ago
Markdown supported.
Become a member to join the discussionEnroll Today
Member comments are a way for members to communicate, interact, and ask questions about a lesson.
The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io
Be on-Topic
Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.
Avoid meta-discussion
Code Problems?
Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context
Details and Context
Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!