Using Git Bisect

[@SaschaRissling]

this is hands down one of the best tutorials i've ever seen. simple, straight forward, just as much context as needed. thank you

[@Rhoso7]

Short, digestible, and sweet. Ty

[@kevinlong4657]

Thanks for this . Bisect is one of those things I’ve seen but really had no idea what it did . Quite easy to understand with you explanation.

[@hansbrackhaus8017]

Thank you for valueing my time, and the time of everyone else.

[@MurciSV]

Thank you for this. Simple and straight to the point, yet fully comprehensive.

[@danieladesanya5374]

very straightforward and well-explained, welldone and thank you

[@RichardHoogstad]

Just what I need it, thanks for sharing and good compact description on how to get this to work

[@howarddo618]

I just use bisect today on my job, thank u for the guide!

[@ahmedam77]

It's the first time I know the usage of that command Thank you so much for your time and efforts :)

[@AndrewVanSlaars]

So glad you found this helpful! I remember when I first discovered this... I actively looked for old, low priority bugs to track down and fix :)

[@jackkendall6420]

This is what every explanatory video on youtube should be like

[@hectorordonez3464]

Great way to explain the use of git bisect, thank you!!!!

[@just_morby]

top tier explanation and guide thank you for this!

[@Dehhloki]

Very good Andrew, thanks for sharing! ❤

[@hetroxity]

whooah bro thank you so much .. i was stuck with this school project ..you came in handy..Godbless from kenya bro

[@malharjajoo7393]

It is important to understand here that this assumes the commits (within the specified range, by the user) are ordered as: [ good, good, good, ......, bad, bad, bad ] otherwise the logic will not make sense. The standard binary search algorithm assumes that inputs array is sorted according to some way such that search space can be halved (by interactively asking "yes" or "no").

[@Knight_Alonne]

Well explained, to the point explaintion 👍

[@AndroidandTechSolutions]

Excellent explanation!! Keep it up. Thanks a lot the video 😊

[@RogerBarraud]

Good, concise tutorial - Thanks!

[@yash1152]

1:37 can it be used in reverse scenario? that the initial commit is bad, and latest one if good, and you want to find out which commit fixed the issue? i mean yeah, if you intentionally and consistenly give the negated answers, then ofcourse yes. but i am asking for automatically

[@sagarajayathilaka]

Great video, Thanks a lot.

[@daephx]

Seems extremely useful but might take some time for me to wrap my head around it.

[@Develoquent]

How can i get to the top of the working tree? git bisect start says i need to..

[@talkohavy]

What does it mean "put us back into a good working state"? Is it like a hard reset? Or a soft reset? Because what if that bad commit contained some good stuff in it? Or what if the commits that followed it had some good stuff in it? Thank you for the video.

[@AndrewVanSlaars]

You end up in a detached head state. Being back in a working state here means you are put back where you started. This process is only to identify a branch, it doesn’t do anything to mitigate the problem. You learn the commit that introduced the problem and from there it’s up to you to figure out the specifics and decide how to fix it.

[@talkohavy]

@@AndrewVanSlaars Got it! Thanks for that :) Very very useful tool then. I never used it out of fear it would do the mitigations for me. Good to know!

[@renilbabu7181]

This is awesome.

[@bernardleech5007]

For oh-my-zsh, you can use these aliases: gbs = git bisect gbss = git bisect start gbsg = git bisect good gbsb = git bisect bad gbsr = git bisect reset

[@AndrewVanSlaars]

Awesome! I’ll have to commit (no pun intended 🙂) those to memory!!

[@Eviloves]

Cool trick, i liked it! thank you very much!

[@rockrollandfunk2691]

Why did you run more tests... Were you looking to verify how many versions contained the bug?

[@AndrewVanSlaars]

Each time I provided feedback, it checked out another commit so I tested and provided feedback so it could determine the commit with the bug. I did a couple iterations in the video without narrating it to avoid the video being too repetitive. Sorry if that made something unclear.

[@rickvian]

this is so powerful

[@fiddling_tech2150]

Thank you!

[@amitbansal7754]

So good.

[@jamesmorgan4397]

great thanks!

[@grainfrizz]

Super awesome

[@parasite6731]

Do you know, your video is being used in the corporate training.

[@AndrewVanSlaars]

I didn’t know that, but it’s on KZbin for people to learn, so I think that’s great!

[@antwanwimberly1729]

Wan 🇮🇱 France 🇫🇷