I'm checking the changes between tags with git log --pretty=oneline v5.4.1...v5.5.0 to create a changelog for the new release. Currently it is a bit painful, because I can't understand most of the commits (even with issues linked).
I think when merging a PR into master we should squash everything into 1 commit using Conventional Commits. From there we maybe could autogenerate changelogs.
I'm checking the changes between tags with
git log --pretty=oneline v5.4.1...v5.5.0to create a changelog for the new release. Currently it is a bit painful, because I can't understand most of the commits (even with issues linked).I think when merging a PR into master we should squash everything into 1 commit using Conventional Commits. From there we maybe could autogenerate changelogs.
The most common used Editors and IDE's have plugins to help you with this commiting style. See: https://plugins.jetbrains.com/plugin/13389-conventional-commit