| description |
|---|
Get an overview of how we use Git commit messages to communicate within the team. Plus, seven rules to make great messages. |
Git commit messages are a way to communicate change to fellow developers. To communicate change understanding context and why that change is necessary is important. We want all our repositories to have a commit log that is easy to consume and understand.
Please take a look at these seven rules for great git commit messages:
- Separate subject from body with a blank line
- Limit the subject line to 50 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how
Before starting a new project discuss with the team and agree to a consistent commit message strategy.