All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Why Conventional Commits Is a Flawed Standard for Commit Messages

By

Sumner Evans

5h ago· 8 min readenOpinion

Summary

This article argues that Conventional Commits, a widely-used standard for formatting commit messages in software development, is a flawed and counterproductive practice. The author contends that the standard encourages developers to focus on the wrong aspects of version control (like formatting and categorization) rather than writing meaningful, descriptive commit messages. It claims Conventional Commits fails to deliver on its promises of improving changelog generation, semantic versioning, and developer communication, ultimately making commit history less useful and more bureaucratic.

Key quotes

· 3 pulled
Conventional Commits is an actively bad standard which encourages focus on the wrong things and fails to deliver on its promises.
A lot of people swear by it. I swear at it.
Even though it is used by a large number of popular open source projects, Conventional Commits is an actively bad standard which encourages focus on the wrong things.
Snippet from the RSS feed
You’ve almost certainly encountered Conventional Commits before. It may have reared its ugly head in the changelog of an open source project you’ve used. It may have been the enforced commit format for an open source project you contributed to. A lot of p

You might also wanna read