type
status
date
slug
summary
category
tags
icon
password
In Git, a standard commit message typically follows these conventions (Angular convention is one of the most popular):

1. Basic Format

2. Type (Required)

Common prefixes (lowercase):
  • feat: new feature
  • fix: bug fix
  • docs: documentation changes
  • style: code formatting changes
  • refactor: code refactoring (no new features or bug fixes)
  • perf: performance improvements
  • test: adding or modifying tests
  • chore: other changes (build process or auxiliary tool changes)

3. Scope (Optional)

Indicates the scope of the commit, for example:

4. Subject (Required)

  • Use imperative, present tense
  • Start with a lowercase letter
  • Don't end with a period

5. Real Examples

6. Complete Example

7. Recommendations

  1. Keep it concise, but include enough information
  1. Use English
  1. One commit should do one thing
  1. Review changes before committing
“Infinity” in Ethereum approveDialectical Thinking: A Guide to Proper Usage
Loading...
Zhenye Dong
Zhenye Dong
Product Manager | New Dad | New Blogger
Latest posts
The Crying Test: A Guide for Setting Rules
2025-2-6
Parenting Note: Learning to Say Goodbye
2025-2-6
Parenting Note: Why laughter Can’t neutralize Tears?
2025-2-6
How to display [[roam/js]] results inline in Roam Research?
2025-1-5
Using the IMAGE Function to Display Pictures in Excel
2025-1-4
Understand Events in EVM
2025-1-3