There are a bunch of tools that take your commits and converts them into release, like semantic-release. There's nothing wrong with the tools and their authors literally. It's fantastic tools that are mostly used the wrong way.
In a nutshell, the idea of any of these tools is pretty basic. They take your commits and generate releases base on your git history.
But take a breath before adding such a solution into your daily project workflow. Firstly ask yourself, do I write my git messages for end-users describing the motivation and changes of public API, or am I just putting internal stuff there?
So, the main idea of this post is if you don't write releases by yourself, you don't care about the end-users; you don't help them; you just add a fancy tool for yourself, nothing more.
Top comments (0)