Re:AI Commits – a CLI that writes your commit messages for you
by Narushia on Tuesday February 14, 2023 @02:33PM
(#34794708)
I personally try to always include at least a short explanation on why the change was done, unless it’s self-explanatory. But I’m under the assumption that most people don’t do this because they already have that info in a relevant issue or merge/pull request. Which I think is a fine approach, especially if you leave the relevant link or identifier to the commit message.
Re:AI Commits – a CLI that writes your commit messages for you
by gerad on Tuesday February 14, 2023 @02:56PM
(#34795039)
In my experience ticketing systems come and go, but the commit history remains forever (yay dvcs), so it's a good idea to summarize the why in the commit message - even if it's already also somewhere else.
That said, a lot of my personal projects that will never get published are just "foo" messages.