News for hackers. Stuff that matters.

A comment on Coding tip: Leave your code in a broken state. Parent comment

Re:Coding tip: Leave your code in a broken state by pdenya on Thursday January 16, 2014 @07:18PM (#7073429)
It's no trouble at all to work on a personal branch and merge it back in once it's fixed/complete. Especially if you're planning on doing it and are using a tool like git flow.
[ Parent | on HN ]
Re:Coding tip: Leave your code in a broken state by CUViper on Thursday January 16, 2014 @07:55PM (#7073596)
If you leave broken commits in the history, you'll make it very hard to use tools like "git bisect". You can "skip" broken commits, but that should be an occasional exception. It doesn't matter if that was on a personal branch either, because once you merge it's all part of the same graph of commits.

I have no problem with broken commits locally, but I don't want to see those in a public tree. Merge or rebase with squashing, please.

[ Parent | on HN ]
Re:Coding tip: Leave your code in a broken state by narsil on Thursday January 16, 2014 @09:34PM (#7073945)
A rebase in the personal branch that squashes the broken commit into the ones that fixed it would remove any traces of broken code in the master branch.
[ Parent | on HN ]