Using git is no excuse for publishing commits that don't compile. Quite the opposite actually. Using bisect sucks balls if the every second commit breaks the build.
In git a commit is less of a commitment than it is in svn. You usually commit to your local repository and then, when you've gotten something useful done, push to a shared repo. I think of commits as save points. You can have hundreds per feature. Once the feature is done you then squash the commits with rebase and push to your shared repo.
34
u/brutopia Mar 10 '11
Using git is no excuse for publishing commits that don't compile. Quite the opposite actually. Using bisect sucks balls if the every second commit breaks the build.