Re:Commit often, perfect later, publish once: Git best pract...
by jollybean on Sunday July 04, 2021 @02:06PM
(#27731494)
" Change a few lines in an afternoon? Nobody cares about the history."
If you changed a couple lines of code as part of a module refactor or something i.e. ongoing changes, then sure.
But if you were fixing a bug or doing some very specific thing, those are actually the times where hyper-specific contextual commits are necessary.
Git is this generic tool for which we still have not yet learned all the best practices and idiomatic usages.
Probably there should be a handful of types of commits, not more than 3-5 i.e. 'change' 'bug fix' 'upgrade' 'internal release' 'major release' (these are probably bad examples).
If you changed a couple lines of code as part of a module refactor or something i.e. ongoing changes, then sure.
But if you were fixing a bug or doing some very specific thing, those are actually the times where hyper-specific contextual commits are necessary.
Git is this generic tool for which we still have not yet learned all the best practices and idiomatic usages.
Probably there should be a handful of types of commits, not more than 3-5 i.e. 'change' 'bug fix' 'upgrade' 'internal release' 'major release' (these are probably bad examples).