Stop Using Conventional Commits
The author argues that the Conventional Commits standard is flawed because it prioritizes commit types over scopes. They contend that developers and debuggers benefit more from knowing which part of the codebase was modified rather than the nature of the change.
Why it matters
Standardization in software development is critical for team collaboration; this critique challenges widely accepted industry practices for version control.
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 people swear by it. I swear at it.
The article presents a subjective technical opinion on software engineering workflows without political or social bias.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in