Conventional Commits – The Best Commit Style I’ve Used

Here we go. It’s my second article. So, before going deep into actual development stuff, I thought I’d write about a good developer practice. Something that improves productivity and teamwork — something that’s equally important as coding and engineering. A good commit history. The first time I found out about proper commit styles was from one of my friends. He wrote an article about common commit styles. You can read it here . He covered multiple styles in that article. In this one, I’m only going into my favorite style — Conventional Commits . You can find the official Conventional Commits specification here . It is heavily inspired by the Angular Commit Guidelines . Now, let’s start. Why Even Use a Commit Style? When you get into development, you are definitely going to use a version control system like Git. And when you look at the commit history, you should be able to easily determine: What changed Where it changed When it changed And sometimes even why it changed Even if you come