Well, you may hold these truths to be self-evident, but that's hardly an argument. And since you say "It's likely what your team uses, as it is the commit message style that is typically recommended as a "best practice" you acknowledge that you hold a minority opinion.
"What I'm saying is self-evidently true" is unlikely to sway anyone.
And I find it dishonest to phrase that as "The psychology portion isn't subjective".
From your colleague:
> The reason that the "subject-first" approach is used is to get contributors to talk specifically to the impacts made to the software itself, rather than talk about themselves and their labors.
I don't recognize that description at all about the majority opinion. Yes, some people write terrible commit messages, but that's not the best practice you seek to upend.
> Of course it's the state after the commit, why would I talk about what was
You'd be surprised. It's more common in bug reports, but I've seen this in commit messages too.
>> Are version numbers ever decreased? > They have been,
Oh, really? Do you have an example?
> In any case, I'm not here to quibble about commit message formats.
Thanks for clarifying that you base this policy on nothing but your subjective opinion, that there is no research to support it, and that everyone else is doing it wrong, because your subjective is clearly objective.
Nothing wrong with that. I do have a problem with you misrepresenting this as objectively better, with a handwavy "scan in F shape". Don't say it's based on research when it's just your "common sense". That's unprofessional.