changelog-format

Generate release notes from conventional commits by parsing Git history and mapping commit types like feat or fix to Keep a Changelog sections. This categorizes log entries automatically, producing a structured unreleased section for your changelog.

The Keep a Changelog format structures release notes into standardized sections such as Added, Fixed, and Documentation. It enforces consistent, machine-parseable changelog entries by mapping conventional commit messages to these specific categories.

Automate changelog generation in release pipelines by parsing conventional commit history and applying a Keep a Changelog style mapping. This extracts commit entries and generates unreleased sections automatically, ensuring consistent release notes across deployments.

You need conventional commit messages in your Git history to automate Keep a Changelog generation. The tooling requires standardized commit formats to map entries into sections like Added and Fixed, along with a configured changelog style mapping.

Conventional commits are mapped to changelog sections by parsing commit types and categorizing them into Keep a Changelog entries like Added, Fixed, and Documentation. A configured style mapping in the tooling translates each commit type to its corresponding section.

Non-conventional commit messages cannot be automatically categorized into Keep a Changelog sections. The parsing mechanism relies on conventional commit formats to map log entries, so inconsistent Git history prevents accurate generation of unreleased sections.