Your Git Log Should Tell A Story

Your Git Log Should Tell A Story

Have you ever been debugging an annoying new bug and realised that the simplest way to track it down would be to look at what changed in the code since the previous release, where the bug wasn't there?

There are different ways to do this, a quick one is to run git log and to skim through the commit messages looking for something suspicious. That is, if the commit messages tell something useful.

We software developers take a lot of care in crafting readable and efficient code, but too often not enough in writing informative commits. It is not uncommon to see logs like this (fictitious) one:

Read full article from Your Git Log Should Tell A Story