What is the use of commit messages?

I fought asking this question, but here it is. I have been using source control from several years for several projects using different systems (svn, hg, git), and I learned how to improve my posts by following the instructions, etc. But, as far as I remember, I never looked at them.

So ... how do you profit from your own commit messages? When I need to go back because I broke something and I need a new beginning, I usually go back to the last "node" (where I started or merged the branch). I write these messages only for people watching the project, who are interested in what is happening?

Hi

+5
source share
6

" , " - Boss

+6

"" . , :

, - , . VCS (ClearCase). , , . , , .

, , , ( ), , , .

Update

, , . , , , . , , , , , .. , . , , , , . , .

+7

, . . , , .

+4

, , - , - , . , , .

+3

/. , , / /. , , .

+1

, , ? : " ?" " ?". , , , .

, ,

  • An error has occurred and you want to find when this part of the code was last modified.
  • You decide to undo some changes and you need to decide which version should return to

For any of these features, without good commit messages, you will be left to look at the differences for each individual commit until you find what you were looking for in the code.

+1
source

All Articles