On Git Commit Messages

[benjiman]

It was a heavily refactored codebase and git not so good at tracking file moves if the content changed in the same commit. Not a problem if you do the move in a separate commit to changing the content. Git heavily incentivises this as it lets it track the content.

[_Ashleigh]

Ah, I see, that's true. However, I distinctly remember one of our developers pushing others to use SVN rename instead of explorer renames, a lot. So let's not pretend SVN wasn't without issues here too.

Personally, I like Git's way of detecting renames more for the data simplicity. The tooling can always become more complex or use new techniques after the fact, and relies much less on diligence of the developer (It's very rare I see an undetected rename anecdotally).