Set up a CHANGELOG system that avoids merge conflicts

[jtannas]

When there are multiple people contributing to a project and there's a single CHANGELOG.md file then there can be a lot of merge conflicts.

I've seen in rubocop that they use individual changelog files for unreleased changes and then they're put into the official changelog during a release.

Take a look around at how this works and if it can be automated.

[jtannas]

This looks like a promising starting point https://github.com/marketplace/actions/changelog-ci

[jtannas]

Doing my own thing since Epoch versioning isn't common enough to have many tools supporting it.
Figuring it out here: https://github.com/jtannas/release-collator