I have a quite strict solo-SCM workflow as well (including PRs!). The reason is that the SCM is not just a tool - the history of the codebase follows the thoug

I have a quite strict solo-SCM workflow as well (including PRs!). The reason is that the SCM is not just a tool - the history of the codebase follows the thought process of the developer. More structured history == more structured thinking. Cleaner history == cleaner thinking. Documentation (traceability etc.) is certainly a benefit, but in this sense, it's part of the smaller picture.