3 ms·
There are some tools that basically don't support this. GitLab is the biggest offender: 1) default view is all commits in a MR squashed together 2) messages b
by stefan_ 8y ago
There are some tools that basically don't support this. GitLab is the biggest offender:
1) default view is all commits in a MR squashed together
2) messages beyond the title hidden under a click on some micro expand icon
3) going through a MR commit by commit means clicking on an individual commit, waiting for the damn thing to load it's view for 10 seconds, then when you're done you have to go backwards and do it all again
- dcosson 8y agoWe use the same settings in Github of squashing PR commits. I guess it's a matter of preference but IMO this workflow is a better version of what the article describes. You get the best of both worlds, you end up with a very readable history of commit messages, where each one describes a single feature or unit. But while you're working you don't have to break your flow to write documentation every time you commit, or go back later to rearrange/rebase commits.