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 ]
There are no comments on this comment yet.