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 krupan on Thursday January 16, 2014 @06:05PM (#7073121)
Have you heard of distributed revision control? Local check-ins are awesome.
[ Parent | on HN ]
Re:Coding tip: Leave your code in a broken state by pipeep on Thursday January 16, 2014 @06:10PM (#7073133)
Unfortunately, that doesn't keep some idiots from pushing broken code to `origin master`.
[ Parent | on HN ]
Re:Coding tip: Leave your code in a broken state by kodablah on Thursday January 16, 2014 @06:41PM (#7073267)
Why can they do so on a mature project? Why can they not only push to their branch, have the repo have commit/push hooks for fast linting, have CI builds for each commit, and only merge into master when comfortable (e.g. after QA)? And if it's a fairly new project and they're working in master directly, what's the harm of broken code?
[ Parent | on HN ]
Re:Coding tip: Leave your code in a broken state by jamesadney on Thursday January 16, 2014 @06:48PM (#7073294)
Even non-idiots make mistakes. Use the pre-push hook that comes with your repo: https://github.com/git/git/blob/master/templates/hooks--pre-...

Then, just mark your commits with WIP.

[ Parent | on HN ]