Git Bisect | How to use Git Bisect | Learn Git

Watch this step-by-step Git tutorial to learn how to use the Git bisect command to quickly find a specific commit in your repo's history. Learn how to use Git bisect to discover where a bug or issue was introduced into a code base, leveraging commands like Git bisect start, Git bisect good, Git bisect bad, and more.
GitKraken Client was used in this tutorial video. Try using Git bisect with GitKraken Client for free!
bit.ly/3tFmE5m
The Git manual section about Git bisect: git-scm.com/docs/git-bisect
Navigate with Chapters:
0:00 Git bisect Introduction
0:33 Git bisect overview
2:37 Git bisect start
2:49 Git bisect bad
3:11 Git bisect good
4:31 Git bisect reset
#gitbisect #gittutorial #git #advancedgit #gittips #gitcommands

[@shankar7435]

Best explanation I could understand after searching for several hours. Thanks.

[@Firecul]

I never knew about bisect, I've always just used GitKraken (or other gui) and either viewed history/blame of a file or clicked through the commits if the repo was small enough.

[@MarkT]

I just asked chatGPT: Why does learning git make me sleepy?
Ans: "Learning Git can sometimes be overwhelming and tedious, especially if you're not used to working with version control systems. It requires a lot of concentration and attention to detail, which can be mentally exhausting. Additionally, the technical jargon used in Git can be confusing and hard to follow, which can further contribute to feelings of fatigue or boredom.
Furthermore, if you are trying to learn Git after a long day at work or when you're already feeling tired, your brain may not be in the best state to absorb new information. Learning Git requires a lot of focus and mental energy, so it's important to approach it when you're feeling refreshed and alert.
If you find yourself getting sleepy when learning Git, try taking breaks frequently, breaking down the material into smaller, more manageable pieces, or finding ways to make the learning process more engaging, such as by following along with a video tutorial or working on a small project to apply what you've learned."

[@antoniohaluzan3396]

I can see bisect useful only when there are big amount of commits and if file is modified a lot by a lot of people. Otherwise I would check the file history and see every single commit of a file, who did the bug and when.

[@Benw8888]

this is less useful when you need to run code to check if there's a bug; then, binary search helps a lot

[@aliciafaulkner416]

This was created at the time there was no meaningful GUI whatsoever, and people weren't able to have multi-monitor to have git and their code editor/compiler showing at the same time. But with gitkraken and multiple screens, I don't see any reason to use biset unless someone refuses to increase productivity by using git gui client.

[@lgiorgos1]

@@aliciafaulkner416 I really don't get it how this feature exists even before meaningful GUIs. I mean, is there any case that git blame cannot help with?

[@aliciafaulkner416]

@@lgiorgos1 I have never used bisect myself and only see how it can work from my manager who is in his 50s who is very old school, using only one monitor, ctrl+tab between everything, never even splitting screen to show more than one thing (linux). He uses it only for finding build failures started between two point in history. It basically streamline the branches switching automatically and you just need to answer yes or no. It saves him like 1 minute of work whenever he needs to do it.

[@amiv220]

​@lgiorgos1 git blame will not help if you don't know which part of code introduced a bug exactly, but it is reproducible. Then, you can narrow down to the commit where it started and look at the changes. I don't use it often, but it helped me a lot few times.