Juri Strumpflohner mainly operates in the web sector developing rich applications with HTML5 and JavaScript. Beside having a Java background and developing Android applications he currently works as a software architect mainly dealing with the .Net technology stack. When he’s not coding or blogging about his newest discoveries he is practicing Yoseikan Budo where he owns a 2nd DAN. Juri is a DZone MVB and is not an employee of DZone and has posted 51 posts at DZone. You can read more from them at their website. View Full User Profile

Choose Your Commit Messages Properly

06.14.2012
| 3821 views |
  • submit to reddit
I already wrote a couple of posts about version control stuff and best practices related with it. So today, what about proper commit messages?
How often did you take a look at the history of some file/folder?? It's just the best backup system you could have and that's one of the main purposes of a VCS (forget about branching, merging etc for a while ). And if you did look at your commit messages, were they meaningful?? Did they make any sense to you?? So often they don't, right? Messages like...
  • method 'SomeMethodInAClass' modified
  • production-build
  • added some files
  • fixed some bugs
  • ...
...they just don't say anything, right?? You have to open some kind of comparison editor and directly look at what actually changed.

Instead...

When looking at the 1st sample comment "method 'SomeMethodInAClass' modified", what would you think about this comment as a (more expressive) alternative:

Bugfix: changed LINQ query to return all entities EXCEPT the current one
Now assume you're currently searching for an issue you're having related to the reading of some entities...I bet this message would jump on your eyes immediately!

So..

..the history excerpt from your VCS should nearly be something that you could directly copy and paste as a public version history on your webpage.

Published at DZone with permission of Juri Strumpflohner, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)