I like your article very much and believe that the structure you offer can lead to meaningful and better commit messages.
It will help me improve my git commits :).
There's only one little thing that I don't quite understand: "...Use the imperative mood, as in "Add ability to export to JSON" (not "Adding" or "Added")..."
Why the imperative mood (I'm actually using "adding" or "added")?
Thank you for your reply :).
I think there is a misunderstanding with my question.
My question is, why should we use imperative?
Is there a logic or rule that says using the imperative mood in the comment section is better?
Hello Rubin,
I like your article very much and believe that the structure you offer can lead to meaningful and better commit messages.
It will help me improve my git commits :).
There's only one little thing that I don't quite understand:
"...Use the imperative mood, as in "Add ability to export to JSON" (not "Adding" or "Added")..."
Why the imperative mood (I'm actually using "adding" or "added")?
Imperative of that would be add instead of adding or added
imperative because it tells me what that commit accomplishes, not what the developer has done.
Thank you for your reply :).
I think there is a misunderstanding with my question.
My question is, why should we use imperative?
Is there a logic or rule that says using the imperative mood in the comment section is better?
I think this blog explains that danclarke.com/git-tense