We 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 de

We 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.