changelog

You can auto-generate release notes by parsing git commits using the conventional commits format. The tool extracts commit types and descriptions, categorizes them into features and bug fixes, then formats and inserts the entries into CHANGELOG.md.

Conventional commit parsing for changelog generation extracts the type, scope, description, breaking changes, and issue references from your commit messages. It then groups these parsed elements into categorized markdown sections for your release notes.

To update CHANGELOG.md automatically during PR merges, run the changelog generator in your repository. It parses the merged pull requests and commits, formats the changes into standard markdown, and inserts the new release entry at the top of the file.

Yes, you can categorize git commits into Features, Bug Fixes, Documentation, Refactoring, Performance, Tests, Chores, and Breaking Changes. This categorization relies on parsing conventional commit messages to organize release notes clearly.

Yes, conventional commits are required to automatically parse type, scope, and breaking changes. This structured commit format allows the changelog generator to accurately categorize changes and format them into standard markdown entries.

The best way to prepare release notes is to run the changelog generator on-demand during releases. It parses recent commits and pull requests, categorizes the changes, and updates CHANGELOG.md with formatted markdown entries.