Commit Message Guidelines
When to Use
- You need a high-quality Git commit message.
- You want consistent Conventional Commits formatting.
Procedure
- Identify the primary change and select the Conventional Commit type.
- Write the subject line in 50 characters or fewer.
- Add a blank second line.
- In the body, explain why the change was needed and the key details.
- Prefer "Because there was an issue with ..., fix ..." over "Fix ...".
Conventions
- Use the Conventional Commits format.
- Prefixes:
feat:,fix:,docs:,style:,refactor:,test:,chore: - Example:
feat: introduce Devise to provide authentication
- Prefixes:
Converted and distributed by TomeVault — claim your Tome and manage your conversions.