Hey, I'm the original co-author of the "Conventional Commits" spec. Although, I should give credit where credit is due, and say that it evolves directly from A

Hey, I'm the original co-author of the "Conventional Commits" spec. Although, I should give credit where credit is due, and say that it evolves directly from Angular commit conventions. I started adopting these conventions with the goal of automating releases, both on my open-source and on the services I was working on at npm (I've since brought the practice to my team at Google). I very much did not want to introduce road blocks to folks committing to their own branches -- which is what the "rewrite the message when you squash" advice grows from. Here's a post I wrote on how my team uses Conventional Commits in our release process: https://dev.to/bcoe/how-my-team-releases-libraries-23el https://dev.to/bcoe/how-my-team-releases-libraries-23el