4 ms·
This is why the best Git workflows IMO involve rebasing and squashing the branch down to a couple of well-defined "logical commits", then merging that (with --n
by nerdponx 5y ago
This is why the best Git workflows IMO involve rebasing and squashing the branch down to a couple of well-defined "logical commits", then merging that (with --no-ff of course) into master/main/trunk.
This forces individual programmers to think somewhat carefully about leaving a sensible commit history behind.