Creating a changelog entry with changelog-management

by gerph
macOS ◆ xterm-256color ◆ fish 107 views

The changelog management tool allows you to create change logs for individual branches, and later collate them into a master change log at release time. This video shows the process of creating a changelog entry for a new branch.

Each changelog entry is created in a separate file with a standard structure - following the https://keepachangelog.com/ style. The sub-command edit will launch your editor with the template to fill in, or the prior change on this branch. To create the record of the change, the relevant section (‘Fixed’ in this instance) is updated to explain what has been changed. When you leave the editor, the change is staged for commit.

The current changes, which may incorporate many branches, can be displayed with the sub-command current. This reads all the current changes and displays them in a unified view showing the state of this release. In this instance, the change can be seen listed alongside all the changes that have been merged from other branches.

When you’re ready to release, the collate sub-command (not shown) can be used to store the state of the release in a separate file, and clear out the ‘current’ directory of files, ready for the next release.

At any time, the full changelog, showing all release notes, can be generated with the sub-command full-changelog.

Each change is stored in a separate file, named for the branch. Because these files are separate, when it comes time to merge the branch to the main line, there will be no conflicts - which would be the case if a single changelog file were modified on each branch.