<story><title>Git-cliff – Generate changelog files from the Git history</title><url>https://github.com/orhun/git-cliff</url></story><parent_chain></parent_chain><comment><author>epage</author><text>While auto-generated changelogs aren&amp;#x27;t the best, they are better than nothing.  Too often I&amp;#x27;ve seen projects without a changelog which is especially annoying when dealing with breaking changes.&lt;p&gt;I&amp;#x27;ve been considering switching to a changelog generator, either from Conventional Commits or from a folder of files just to avoid merge conflicts with the CHANGELOG file.&lt;p&gt;If people want enforcement of Conventional Commit, check out &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;crate-ci&amp;#x2F;committed&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;crate-ci&amp;#x2F;committed&lt;/a&gt;</text></comment>
<story><title>Git-cliff – Generate changelog files from the Git history</title><url>https://github.com/orhun/git-cliff</url></story><parent_chain></parent_chain><comment><author>joshuanapoli</author><text>We’ve been using charmixer&amp;#x2F;auto-changelog-action to generate release notes. This action makes nice references to GitHub pull requests. The release notes are attached to a GitHub release by an action. This turns out to be an invaluable reference for SQA and Product Manager for testing and creating customer-facing release notes.&lt;p&gt;One downside is that we run into trouble with GitHub API rate-limiting.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;charmixer&amp;#x2F;auto-changelog-action&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;charmixer&amp;#x2F;auto-changelog-action&lt;/a&gt;</text></comment>