Now and then we want to know the evolution of a software we are working on. For some time I thought the Git log of a project was enough, but the truth is there is much noise in there. In addition to the noise, depending of the project, sometimes some not no techie people need to read the product history and doing a git log is not an option for them. A solution many people found for these problems is to keep a changelog file.
For a long time, the problem with changelogs was that they were hard and expensive to maintain, too much time was needed. Fortunately, the AngularJS community created some Git commit message conventions. Definition is a step for automation and Node.js conventional-changelog was created. The main problem with the Node.js version of the conventional changelog is that it doesn’t have an executable and many of my projects are not in Node.js . There is also a Grunt version, but I don’t want to add a Gruntfile to many Ruby projects just to be able to generate a changelog. I thought about creating a pull request adding an executable to the Node.js version, but I also wanted to be able to generate changelogs by dates, not just versions, as until now I haven’t need to use versions in web applications and separating the changes by date seems more natural to me.
Conventional Changelog Ruby was born a tool to easily generate changelogs with Rubygems and Git as the only dependencies. A big addition over the other versions is that changelogs by date are also supported. For more and up to date info, please refer to the README.