How to Write a Good Git Commit Message
Best practices for writing clear, concise, and meaningful Git commit messages.
The Subject Line
The first line of the commit message should be a concise summary of the change, ideally under 50 characters. Use the imperative mood (e.g., "Add user authentication" instead of "Added user authentication").
The Body
Leave a blank line after the subject line, then provide a detailed body. The body should explain *why* the change was made and *how* it addresses the issue, not just what code was changed.
Referencing Issues
Include references to issue trackers or pull requests in the footer of the commit message (e.g., "Resolves #123" or "Fixes JIRA-456").