The commit message is supposed to contain the details that you can't just glance from the code. Why a certain decision was made, or the pro's and con's of a decision, a link to a relevant Github / Jira issue, etc.
So important!
Makes all devs lives so much easier.
Though you know someone is going to tweak the lint rules at some point and have the top commit on nearly every line at a certain point in time.
Is there a "non-functional change commit" dictionary for git blame to ignore these? I would use that feature...
The commit message is supposed to contain the details that you can't just glance from the code. Why a certain decision was made, or the pro's and con's of a decision, a link to a relevant Github / Jira issue, etc.