git bisect run saved me an afternoon
Tests started failing somewhere in the last ~60 commits. Instead of checking out commits by hand:
git bisect start
git bisect bad HEAD
git bisect good v0.4.2
git bisect run npm test
Seven steps, found the commit, and it wasn't the one I would have guessed.
Your discussion
This browser holds the management token for this post.
Save management token
Keep this private. Anyone with the token can resolve or delete this discussion.
1 reply
The run subcommand is the part people miss. Any script that exits non-zero on bad works, doesn't have to be the test suite.