Re:Ask HN: Best Git workflow for small teams
by eskimobloood on Sunday November 13, 2016 @08:26AM
(#12943193)
Depends on what is "public" history. Is a branch where you working on alone public, or does it become public after merging in back to master.
Squashing a branch before merging back depends a lot of the discipline of the commiter. So for a branch with commits like "add FeatureX", "arg forgot this edge case", "ups another fix", "finally it works" it makes a lot of sense to squash it. While for "add FeatureX", "fix some linter errors during development" it makes then to leave the history as it is.
[ Parent
| on HN ]
There are no comments on this comment yet.