I’m in the midst of preparing some SCM guidelines for our Subversion users and came across a point of contention with the team. Is there ever a valid use case for someone to make consecutive commits with identical messages?
If you take the approach that a commit message should describe the “what” and “why” of code changes it’s difficult to see a valid case for this. Looking at our history, the instances where this has happened appear to be more out of convenience than anything else and really don’t tell the story of what the code is doing.
Does anyone have any views on the legitimacy of this? Would guidelines (or even pre-commit hooks) be overzealous or is it a reasonable expectation?
Edit: let’s work with the assumption that people are already leaving good commit messages. IMHO, a single word like “updated” or “typo” does not constitute a satisfactory commit message. I would expect to see something more like “Updated colour of submit button to green” or “Fixed typo in instructional copy”. It’s very difficult just to browse a repository log and understand what’s going on in a project without drilling into individual commits if the message is a word or two.
Yes.
Mostly this occurs because of inadequate training in the use and purpose of commit messages. It is a good idea to look for this regularly and approach the individuals doing it to inform them of the importance of good descriptive commit messages. If people understand how to write a good commit message, then the only dups you will see will be the occasional absent-mindedness.