What should the proper workflow be with git-flow

I am new to the whole conventional-“insert-anything-here” part and I really want to do things right. I just read about git-flow, which sounds really reasonable, but when I do a release with it, it tags my release. If I run conventional-github-release or standard-version they do a git-tag as well. NPM version does as well, but I saw I can omit that tag with npm --no-git-tag-version version.

Could someone just give me a proper workflow to:

• Start a feature branch
• After I’m done with the feature, create the changelog and merge the feature
• Do a feature release This can be easily done with git-flow and conventional-changelog, right? The version release on GitHub I can do manually, because conventional-github-releaser I think does a tag as well or something, not sure anymore.

But what if I want a major release? Git-flow will do a tag, then maybe generate changelog with conv-changelog and do a new version with npm version

If Someone would give me a proper workflow for common scenarios, that would be awesome, because I am really confused with all the different cli tools in the conventional- family.

[dobromir-hristov]

http://digital-cult.com/releasing-js-library-github-git-flow-conventional-commits/ Take a look if you have the time. Thank you for your awesome work!

[dobromir-hristov]

git flow release finish release-name -n skips tagging. After that I can change to master, merge with develop (because there is a merge branch commit there), then run standard-version. I could have some hooks in git or npm to add versions in banners in my js or what not. Then I can push everything and only one tag is created. Am I right this time 😄