Autogenerating CHANGELOG.md capability

[apolopena]

Problem this feature will solve

There is no CHANGELOG.md. Creating a Changelog by hand is hard to standardize and maintain and is time consuming especially when new releases come out quicky.

Background

Versioning a project with a detailed, neat and, standardized changelog is an important task. This process is time consuming to do by hand. Tracking changes for releases all one one tidy page is a must have for a well organized project.

Proposed Solution

• Implement github-changelog-generator
• Make the ruby gem install for this silent and quick (omit doc generation) but display a spinner in the terminal.
• Add a rake task for generating CHANGELOG.md without having to pass it any flags, simply run: rake changelog
• The rake task should accept for any flags that github-changelog-generator supports.
• Add a dynamic system to create rake tasks based on starter.ini and gitpod env vars.
• Automatically derive github user and the github project.
• Allow for configuration of --user, --project, --since_tag, and --future_release by default

Constraints and Assumptions

• Support just github for now.
• Requires ruby and as awesome as Gitpod is, the Gitpod environment comes with ruby and rake right out of the box.
• CHANGELOG will require a (git) tag in order to properly output the version number. set this tag as the value for future_release in starter.ini or the most recent changes in the changelog will have a title of UNRELEASED.

Alternatives or Workarounds

Compile changelogs by hand. This will make it almost impossible to standardize though.

Additional context

Time saved doing chores is time gained fixing bugs and coding features 💪🏽