Add a CHANGELOG.md file similar to the format promoted by https://keepachangelog.com. One advantage is greater protability, e.g. if someone forks the project to a non-github forge. Another advantage is additional offline visibility, e.g. for people who update b2luigi via git pull and don't subscribe to the releases.
The advantages are imo not worth a lot of duplicate effort with every release, however, maybe creating a changelog file from gh releases can be automatized. I did a quick google search and there's many projects for that, e.g.
https://github.com/github-tools/github-release-notes: NPM program that can do a all sorts of stuff, create releases from issues and create changelogs from releases. However, modern github has built-in support for releases from issues, so I'm not sure if I need that.
Add a
CHANGELOG.mdfile similar to the format promoted by https://keepachangelog.com. One advantage is greater protability, e.g. if someone forks the project to a non-github forge. Another advantage is additional offline visibility, e.g. for people who update b2luigi viagit pulland don't subscribe to the releases.The advantages are imo not worth a lot of duplicate effort with every release, however, maybe creating a changelog file from gh releases can be automatized. I did a quick google search and there's many projects for that, e.g.