Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Changelog #11

Open
westonganger opened this issue Mar 25, 2021 · 2 comments
Open

Add Changelog #11

westonganger opened this issue Mar 25, 2021 · 2 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@westonganger
Copy link

Please add a changelog so we can see whats changed between versions.

@ilyazub ilyazub added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Mar 26, 2021
@ilyazub
Copy link
Collaborator

ilyazub commented Mar 26, 2021

Agree. Currently, GitHub Releases page can be used as a changelog.

I'll add a changelog based on Keep a Changelog format. In the future, I'd rather automate this stuff with github-changelog-generator or release-drafter. What do you think?

@ilyazub ilyazub added good first issue Good for newcomers and removed help wanted Extra attention is needed labels Aug 18, 2023
@aprescott
Copy link

aprescott commented Jul 10, 2024

Since I just ran into this, trying to determine what was included in a release: I personally find a changelog file separate from GitHub releases notes to be very helpful.

That said, no matter where the changelog is made available, I would ask as an outside dev that the changelog explicitly not be generated from commits or merged PRs. A log of git activity is very different from the higher-level document I'd expect when reading a changelog.

The github-changelog-generator project linked above mentions keepachangelog.com, which also outlines this same guidance:

Changelogs are for humans, not machines.

https://keepachangelog.com/en/1.1.0/#bad-practices:

Commit log diffs
Using commit log diffs as changelogs is a bad idea: they're full of noise. Things like merge commits, commits with obscure titles, documentation changes, etc.

The purpose of a commit is to document a step in the evolution of the source code. Some projects clean up commits, some don't.

The purpose of a changelog entry is to document the noteworthy difference, often across multiple commits, to communicate them clearly to end users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants