Questions About Workflow about gitmoji-changelog

[SturmB]

Hey, @frinyvonnick. 👋🏻

Thank you so much for your thorough explanation. I like your naming convention of the tagged commit and may adopt it—or something very similar—as well.

I understand now the difference between a tag's message and GitHub's release description for a tag. I also understand your desire to not integrate GH's Release API into gitmoji-changelog even though I think there might be a way to do so while still keeping the package usable by non-GH users.

Thanks again, keep up the awesome work, and take care! 😃

[frinyvonnick]

Hi @SturmB 👋

Thank you for posting this issue. I usally name the commit that contains my package.json + changelog changes :bookmark: Release [version]. Here is an example. Tags are a way to link a commit to a version number. In Github exists the concept of GitHub release that let you associate a description to a tag like you see in the link you provided. All I did was copy pasting the portion of my changelog related to the tag I create a GitHub release for. It could be automated since it is possible to create GitHub release through an API but it is really specific to GitHub and gitmoji-changelog tends to be more generic 😄 Hope I answer your questions 👍

Sorry for the delayed reponse.