Sumner Evans, a tech lead at Can/Am Technologies, published a detailed critique of the Conventional Commits specification on June 2, 2026. In his article on sumnerevans.com, Evans argues that the widely adopted commit message format encourages developers to focus on the wrong aspects of software development, potentially hindering productivity and clarity.
Evans explains that Conventional Commits, despite its popularity and use in many open source projects such as Angular and Electron, imposes a rigid structure on commit messages that can distract from meaningful content. He highlights that the format’s emphasis on categorizing commits by type and scope often leads to mechanical compliance rather than thoughtful communication. Evans advocates for more flexible and context-driven commit messages that better serve development teams.
The critique challenges a standard that many developers and projects have embraced for its perceived benefits in automation and changelog generation. By questioning the value of Conventional Commits, Evans contributes to ongoing discussions about best practices in software engineering workflows. His perspective aligns with a broader movement toward prioritizing developer experience and practical clarity over strict adherence to conventions.
Evans’ article, titled "Stop Using Conventional Commits," spans 1,873 words and is available on sumnerevans.com as of June 2, 2026. The piece has sparked conversations among software engineers about the balance between standardization and flexibility in commit messaging.