Jenniferplusplus
@inthehands The hill I will die on is that version control systems, and thus the messages attached to commits, are for versioning sources, not finished artifacts. Many many attempts to enforce a commit message standard are made in service of turning commit messages into release notes, and this is bad for everyone.
The essential purpose of VCS commit messages is to make commits findable. Do whatever makes them findable for you, the committer.
Paul Cantrell
@jenniferplusplus
Sounds like our personal philosophies are not too far apart. Add “team members” somewhere into your text and the Venn diagram will be close to a circle.
Jenniferplusplus
@inthehands Um, yes, but also no. Commit messages are memory aids, and the more they're asked to do beyond that scope, the less useful they are. So, the level where you add in team members is to recognize that team members might sometimes ask you questions like, "do you remember that bug you fixed? How did you do that? Because I think this situation is similar"
If the author isn't around to ask, the commit messages aren't going to fill that gap.
Paul Cantrell
@jenniferplusplus
I guess I see them not just as memory aids, but also as an index, a map, a summary of diffs: not full documentation, not there to capture discussion, but just a way to answer the question “Where is that thing?” or “What is an outline of the dev process?” If I already have context, I don’t want to have to sift through all the diffs to get the big picture.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.