release-notes-generator

Generate release notes from git commits automatically by analyzing repository history since the last release tag and fetching PR details via gh api. This process parses technical commit data to produce user-friendly messaging for non-technical stakeholders.

Yes, you can create a Slack announcement and a CHANGELOG.md entry from git history at the same time. The process generates three outputs simultaneously: a CHANGELOG.md section, a PR release body, and a Slack message.

The best way to turn technical git commit messages into user-friendly changelogs is to fetch PR titles, descriptions, and labels via gh api, then transform that technical language into clear messaging suitable for non-technical stakeholders.

Yes, you need gh api access to generate release notes for your software project. The process requires access to the repository's git history and PR details fetched through gh api to identify changes since the last release tag.

Yes, this release notes generation approach works for version bumps in software projects of any size. It applies to releases, version bumps, and changelog workflows, analyzing git history to identify changes for projects of varying scales.

Manually drafted release notes are inconsistent with git history because they rely on manual interpretation rather than automated parsing. Automating the conversion of git commits ensures publishable release notes that accurately reflect repository changes.