Automate generating changelogs about antimicrox HOT 11 CLOSED

I'll look into this, but first, Flathub and Fedora submission has priority.

from antimicrox.

Okay, let's stick with that for now! :)

from antimicrox.

I'd close this issue for now, auto changelog generation works fine. We can reopen if more stuff comes up later. 🙂

from antimicrox.

Are there any ways of filtering commits to be mentioned in changelogs (by tags or by names/types of changed files)?
I don't want to fill our changelogs with README updates etc.

from antimicrox.

Requirements for our changelogs:

• describe changes visible for end-users (changing readme, or any similar files doesn't count)
• don't include issues irrelevant for users (for example issues tagged as questions shouldn't be mentioned), I am not sure if issues should be mentioned in changelog at all 🤔
• avoid duplicates (for example if we have bug mentioned by issue and single Pull request fixing it, we should mention only one of them)
• It would be good to use Conventional Commits to have multiple categories

I am not sure about mentioning changes in code, which doesn't affect functionality (I mean cleanups, chores etc).

But in Release descriptions (visible on release site) we should show all the changes on repo since previous release Issues, Merges etc.
It would look there especially good, mainly because it is generated in Markdown and links relevant issues.

from antimicrox.

https://github.com/github-changelog-generator/github-changelog-generator/wiki/Advanced-change-log-generation-examples
Here you can see which labels we can use.
Doing complex config is not possible here, if you want complex changelog, then we'll have to write it manually.

from antimicrox.

We could generate basic log, and later we could cut it using Python script (I can write this script).

from antimicrox.

A simple git commit log command with sed or whatever?

from antimicrox.

I mean, we could generate regular changelog using this generator and later remove all of unwanted commits.

from antimicrox.

Or we could just generate these changelogs using your config and manually remove unwanted pieces (I think it will be the simplest solution, because removing some lines is pretty quick task).

from antimicrox.

For now I just changed labels for sections so that we can manually remove stuff.
We can also play around with section and PR labels: https://github.com/github-changelog-generator/github-changelog-generator/wiki/Advanced-change-log-generation-examples#section-options

So we'll only include e.g. enchantments and bugs, but not docs and packaging, or whatever.

from antimicrox.