unknown

Git commit messages on random pull request branches are deemed unnecessary and time-wasting since they are often irrelevant to the final state of the main branch, especially with modern trunk-based engineering practices. The author advocates for empty commit messages by default and squash-merging PR branches into main to keep commit histories clean. Efficiency and reduction of mental overhead are emphasized, with suggestions for Git and GitHub improvements, including autosave functionality and enhanced branch protection rules.

Git commit messages are useless

Hi, Trunk makes developer tools to solve problems developers hate.

But we also love sharing about what we learn along the way as we speak to engineering leaders!

Trunk.io

Git commit messages are useless.

Git commit messages are useless.

I partially disagree with this. I working for a company where we are asked to keep the commit message very descriptive (more than a single line) when possible and squash commits on merge should be too.
It actually gives us quite a lot of information.
But else I agree

When there are no errors -&gt; “stuff”
When there are errors -&gt; “whole lotta red”
Thank you Eli, for making me not feel trash about my messages.
But on a serious note I feel commit messages on branches become even more irrelevant when you start practices like trunk based development and stacking. You can focus more on output of a unit of work than the history.

<code>alias fcom=&quot;git add . &amp;&amp; git commit -m 'fix'&quot;</code>

I’ve gotten into the habit of describing the goal instead of exactly what was done. For example; “added support for xyz” rather than “installed abc and updated the thing”. Helps when searching for stuff too.

This webpage isn’t really suitable for mobile. Maybe the creator should look into that…Nice article though!