2 ms·
Every time I read something about "how to write good commit messages" it always seems to focus on reading the messages back as a log. That's great if that's how
by onion2k 5y ago
Every time I read something about "how to write good commit messages" it always seems to focus on reading the messages back as a log. That's great if that's how you use commit messages, but I tend to use them more for searching for a specific change so it doesn't really work for me. A more narrative style in commits I might need to go back to makes it easier to find them later.
How you write your commit messages should be driven by whatever you use them for afterwards.
- sudo_chmod777 5y agoDefine 'specific change'. A change driven by a business decision? Don't see how it won't work. A change specific to a component? Try conventional commits with scopes. Code change? You shouldn't use commit messages. Use e.g. `-G`, `-S`, `-L`, etc. instead. By the way if you are not using fzf already, you should.