3 ms·

Having properly separated and single-purpose commits is awesome when running `git bisect` [1] — especially with automatic tests. As well when you revert said co

Having properly separated and single-purpose commits is awesome when running `git bisect` [1] — especially with automatic tests. As well when you revert said commits after the offender is found. [1]: https://git-scm.com/docs/git-bisect https://git-scm.com/docs/git-bisect

marcinzm 7y ago
If you're using a CI that runs on every PR/master merge wouldn't it catch this without the need for git-bisect?
- int_19h 7y ago
  Only if your tests have perfect coverage. And by "perfect" I don't mean lines or branches, but program states.