Yesterday, I wrote about [keeping a CHANGELOG][0] for software projects, and about the <https://keepachangelog.com> project.
I like this slogan on their website:
> Don’t let your friends dump git logs into changelogs.
A CHANGELOG shouldn't be a list of Git commits in a file.
It should be in a human-readable format that's easy for people to read and understand, whether they are technical or not.
This probably isn't the case for the output from `git log`, which may also contain commits like `Refactor` and `wip` that don't mean anything to someone who focused on the higher-level deliverables.
Git logs are great for Developers, but CHANGELOGs are for everyone.
[0]:/daily/2025/07/27/do-you-keep-changelog
format:markdown
processed:|
<p>Yesterday, I wrote about <a href="http://localhost:8888/daily/2025/07/27/do-you-keep-changelog">keeping a CHANGELOG</a> for software projects, and about the <a href="https://keepachangelog.com">https://keepachangelog.com</a> project.</p>
<p>I like this slogan on their website:</p>
<blockquote><p>Don’t let your friends dump git logs into changelogs.</p>
</blockquote>
<p>A CHANGELOG shouldn't be a list of Git commits in a file.</p>
<p>It should be in a human-readable format that's easy for people to read and understand, whether they are technical or not.</p>
<p>This probably isn't the case for the output from <code>git log</code>, which may also contain commits like <code>Refactor</code> and <code>wip</code> that don't mean anything to someone who focused on the higher-level deliverables.</p>
<p>Git logs are great for Developers, but CHANGELOGs are for everyone.</p>