Using Git Bisect

preview_player
Показать описание
Use git bisect to track down the commit that introduced a bug.
Рекомендации по теме
Комментарии
Автор

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

SaschaRissling
Автор

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.

kevinlong
Автор

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

hansbrackhaus
Автор

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

MurciSV
Автор

very straightforward and well-explained, welldone and thank you

danieladesanya
Автор

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

howarddo
Автор

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

hetroxity
Автор

This is what every explanatory video on youtube should be like

jackkendall
Автор

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

ahmedam
Автор

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

RichardHoogstad
Автор

top tier explanation and guide
thank you for this!

just_morby
Автор

Well explained, to the point explaintion 👍

Knight_Alonne
Автор

Very good Andrew, thanks for sharing! ❤

Dehhloki
Автор

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

hectorordonez
Автор

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").

malharjajoo
Автор

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

AndroidandTechSolutions
Автор

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

yash
Автор

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

Develoquent
Автор

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

daephx
Автор

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.

talkohavy