I can't say they are good, because my commit messages get technical, and because I'm not very good at git, but here is my process.
My project is in early stages and I am primary developer. I only have several instances I am supporting.
I upgrade by doing a git checkout and ./rebuild.pl.
Whenever the value of current git pointer changes, it automatically generates a changelog of all the commit messages between the previous pointer and current.
As long as I write clear commit messages, my changelogs automatically contain useful information.
I can also add comments in reply to the changelogs.
All of it is automatically accessible via #meta hashtag
I like their use of alphabetical order within each section, first word being component it seems.
Makes it easier to follow a particular aspect changed, nice one!
5 comments
[ 3.2 ms ] story [ 24.7 ms ] threadMy project is in early stages and I am primary developer. I only have several instances I am supporting.
I upgrade by doing a git checkout and ./rebuild.pl.
Whenever the value of current git pointer changes, it automatically generates a changelog of all the commit messages between the previous pointer and current.
As long as I write clear commit messages, my changelogs automatically contain useful information.
I can also add comments in reply to the changelogs.
All of it is automatically accessible via #meta hashtag
I particularly like the consul changelog https://github.com/hashicorp/consul/blob/master/CHANGELOG.md which follows it.