changelog-curator

You can organize raw commits and merged changes into structured, versioned changelog entries by grouping them by release context. This enforces repository conventions and outputs a ready-to-edit draft aligned with standard templates.

The best way to group unreleased notes by version is to collect changes from multiple contributors and merge commits, then format them into a canonical changelog entry. This outputs a ready-to-edit draft for the upcoming release.

Yes, you can apply consistent changelog formatting across multiple projects and teams. The process enforces repository conventions and formats sections consistently, ensuring all teams follow standard changelog templates.

To handle merge commits when organizing release notes, you process them alongside raw commits and unreleased notes from multiple contributors. The system integrates these merged changes into structured, versioned changelog entries.

Yes, this changelog generation approach works with different release branches. It is applicable to software projects maintaining CHANGELOGs across releases and branches, organizing changes into structured entries regardless of the branch source.

Your changelog draft needs manual editing after generation because the tool outputs a ready-to-edit draft rather than a final document. This allows contributors to review the structured entries, verify the grouped changes, and adjust the formatting before release.