News for hackers. Stuff that matters.

A comment on Commit messages guide. Parent comment

Re:Commit messages guide by schroffl on Saturday April 20, 2019 @10:26AM (#19706661)
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

[ Parent | on HN ]
Re:Commit messages guide by marcinzm on Saturday April 20, 2019 @11:10AM (#19706916)
If you're using a CI that runs on every PR/master merge wouldn't it catch this without the need for git-bisect?
[ Parent | on HN ]
Re:Commit messages guide by int_19h on Saturday April 20, 2019 @10:40PM (#19710256)
Only if your tests have perfect coverage. And by "perfect" I don't mean lines or branches, but program states.
[ Parent | on HN ]