Git is a powerful tool. Once you’ve mastered and , there are endless possibilities. A very useful one is . It helps you find a commit that introduced a certain change in behavior. commit merge [git-bisect](https://git-scm.com/docs/git-bisect) We use a lot in the . The Node.js project has good continuous integration but some bugs are only discovered after a release. With , it’s easy to find the bad commit. git-bisect Node.js project git-bisect Try it! If you want to try out , here is a . At some point, a bug was introduced as you can see by running . Can you find the bad commit? git-bisect demo repository npx mocha test1.js Use this repository to practice git bisect. Automating git-bisect Instead of testing each step manually, you can run with a script. It will use the script at each step and automatically mark the commit, until it finds the . git-bisect first bad commit

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

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

The Power of Git Bisect as Your Debugging Ally

10 GitHub Repositories to Follow

3 Easy Steps to Change Main Git Branch on Heroku

28 Stories To Learn About Markdown

194 Stories To Learn About Git

The Power of Git Bisect as Your Debugging Ally

10 GitHub Repositories to Follow

3 Easy Steps to Change Main Git Branch on Heroku

28 Stories To Learn About Markdown

194 Stories To Learn About Git

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps