3 ms·
Is there any justification for preferring present tenses over past tenses? Past tense ("Fixed ...") makes more sense when looking at a report of what was done.
by muyyatin 16y ago
Is there any justification for preferring present tenses over past tenses?
Past tense ("Fixed ...") makes more sense when looking at a report of what was done.
- crazydiamond 16y agoSeems to be a convention. I prefer past tense too.
- tung 16y agoIt makes a tiny bit more sense when the commits are patches. I don't mind the difference too much; if I'm in a team, I just go with what everybody else does.
- andreaja 16y agoThe code is alive and the code is hungry.
- tomstuart 16y agoThe most objective justification is that Git uses the present tense when it generates its own commit messages ("Merge branch...", "Revert..."), so using the same tense for your commit messages makes everything consistent.
- adolph 16y ago1. Using the past tense is a bit presumptuous on the part of the committer. 2. Using the same tense as the todo list reduces rewriting.