Git Best Practice
Question
Which is a good Git commit message practice?
Hint
Good messages are concise and descriptive.
Explanation
A good Git commit message uses the imperative mood ("Add feature" not "Added feature"), keeps the first line under 50 characters, optionally adds a blank line and detailed body wrapped at 72 characters. The message should explain what and why, not how (the diff shows how). Prefixes like feat:, fix:, docs: (Conventional Commits) help automate changelogs and releases.
Related Resources
Related Lessons
- Best Practices
Learn best practices.
Look up unfamiliar terms
A beginner-friendly glossary explains jargon in plain English — variables, functions, DOM, Promise, and more.
Decode error messages
Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.
Build real projects
Apply what you learned by building guided projects with starter code and solutions.