Stop Using Conventional Commits
In a blog post titled "Stop Using Conventional Commits," the author criticizes the widespread adoption of the Conventional Commits specification, which standardizes commit message prefixes like `feat:`, `fix:`, and `chore:`. The author argues that while the intent is to improve clarity and enable automated changelog generation, the practice often backfires. Developers may spend time debating the correct prefix, leading to friction in code reviews. Moreover, the rigid structure can result in commit messages that are less informative, as developers focus on compliance rather than communication. The author points out that many commits are incorrectly labeled (e.g., a `fix:` that actually introduces a new feature) or use generic prefixes like `chore:` for significant changes. The post suggests that teams should instead prioritize writing descriptive, human-readable commit messages that explain the "why" behind a change, and rely on tools like semantic versioning only when necessary. The author concludes that Conventional Commits are a solution in search of a problem and that simpler approaches are more effective for most projects.
Adopting rigid commit conventions can harm team productivity and message clarity.