Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
jo vo
Courses Plus Student 4,830 Pointsnaming convention?
I have always learned that is best practice to create your new message (-m) in the present tense, like : "add project files".
In your videos you always use the past tense, like : "added project files".
Does it really matter, or is just personal/professional preference?
3 Answers
Matthew Orndoff
9,018 PointsThe preference for present-tense comes straight from the official git repo guidelines for submitting patches.
the body should provide a meaningful commit message, which:
- uses the imperative, present tense: "change", not "changed" or "changes".
Ultimately you can do whatever you want, but I've found present-tense in commit messages to be the standard. I think the most important thing though is to pick one tense and stick with it.
Tracy Trathen
10,468 PointsIt also depends on your company and what they follow for commit message standards. It's great to follow convention, but even better when you're on the same page with your company.
jo vo
Courses Plus Student 4,830 PointsThanks, so it is indeed best practice. However, in this tutorial (which I liked very much) it is being used mixed, so it is/was kind of confusing for me. Thanks for clearing it up.
Maybe a tip, to mention this good practice at the start or end of this course?