release-notes

Generate release notes by analyzing git commits between two points like tags, branches, dates, or commits, and formatting them into client-friendly updates. It groups changes by type and rewrites technical details into plain language for stakeholders.

The best way to create a client-facing changelog is to group commits by features, fixes, and improvements, then rewrite technical messages into plain language. This approach formats git history into readable sections for customer updates and demos.

Yes, you can produce both internal and external release note variants from the same git tags. The tool analyzes commits between specified points and formats the output separately for client-facing notes and internal changelogs.

Rewrite technical commit messages into plain language by grouping git history by change type and summarizing the context. This provides product management with clear, client-ready notes suitable for demos and marketing updates.

Yes, the release notes tool works with branches and dates instead of tags. It supports multiple input points, allowing you to analyze and summarize git history between any two specified commits, tags, branches, or dates.

Automated git changelogs require clear commit context to effectively group changes by type and rewrite technical details. Without sufficient context in the original git history, the accuracy of plain language summaries for stakeholder communication may be limited.