paint-brush
Understanding Git-Bisect, i.e. Use Binary Search to Find the Change that Introduced a Bugby@fhinkel
3,442 reads
3,442 reads

Understanding Git-Bisect, i.e. Use Binary Search to Find the Change that Introduced a Bug

by Franziska Hinkelmann2mOctober 18th, 2018
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

Git is a powerful tool. Once you’ve mastered <code class="markup--code markup--p-code">commit</code> and <code class="markup--code markup--p-code">merge</code>, there are endless possibilities. A very useful one is <code class="markup--code markup--p-code"><a href="https://git-scm.com/docs/git-bisect" target="_blank">git-bisect</a></code>. It helps you find a commit that introduced a certain change in behavior.
featured image - Understanding Git-Bisect, i.e. Use Binary Search to Find the Change that Introduced a Bug
Franziska Hinkelmann HackerNoon profile picture
Franziska Hinkelmann

Franziska Hinkelmann

@fhinkel

Senior engineer at Google. Working on Node.js for @GCPcloud. Node.js TSC member. ❤️ JavaScript. she/

About @fhinkel
LEARN MORE ABOUT @FHINKEL'S
EXPERTISE AND PLACE ON THE INTERNET.
L O A D I N G
. . . comments & more!

About Author

Franziska Hinkelmann HackerNoon profile picture
Franziska Hinkelmann@fhinkel
Senior engineer at Google. Working on Node.js for @GCPcloud. Node.js TSC member. ❤️ JavaScript. she/

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite