At work we always put an issue number (together with a short summary text) in the commit message. The the verbose explenation is done in the issue, where formatting, search and filtering is easier. However this creates a dependency to that issue system.
yeah, trying to convince our product owner to read commit messages wouldn’t go smoothly in my team. Some of them love their tickets…
the dependency to the issue system is unfortunate though, I do miss a “decentralized issue system” doing what git does for version control that would just seamlessly integrate with git and have a nice web GUI for less technical folks.
At work we always put an issue number (together with a short summary text) in the commit message. The the verbose explenation is done in the issue, where formatting, search and filtering is easier. However this creates a dependency to that issue system.
yeah, trying to convince our product owner to read commit messages wouldn’t go smoothly in my team. Some of them love their tickets…
the dependency to the issue system is unfortunate though, I do miss a “decentralized issue system” doing what git does for version control that would just seamlessly integrate with git and have a nice web GUI for less technical folks.
That’s called a mailing list
/s
god, I already struggle trying to find information in github issues, I can’t imagine using email for this
You don’t have to imagine it; you can browse the Linux Kernel mailing list!