Re:Git: Using Advanced Rebase Features for a Clean Repository
by therealmarv on Wednesday August 09, 2017 @06:48AM
(#14967297)
keeping a clean commit log or even strong commit rules is something which I only see as barrier for improving existing code... just thinking of code improvements by PRs which got rejected by bigger projects because the commit history was not "clean enough". History is not always good or pretty in real life... it should be the same on git commits.
[ Parent
| on HN ]
Re:Git: Using Advanced Rebase Features for a Clean Repository
by joshschreuder on Wednesday August 09, 2017 @06:53AM
(#14967330)
To some extent I agree, enforcing it at a project level seems like bikeshedding and not necessarily that useful. On the other hand, like walking people through your house, it's nice to tidy up first to give people a good experience, and the same applies to walking through the history of your change too IMO
Re:Git: Using Advanced Rebase Features for a Clean Repository
by therealmarv on Wednesday August 09, 2017 @06:59AM
(#14967368)
Even software with good and beautiful git histories can be ugly as hell (seen it all) and a good and beautiful house can have some really bad ugly history ;)