Usage with git flow?

Hi,

I like the features in this package, and I would like to know how this can be used in conjunction with git flow (the command line edition). Currently my release process is:

git flow release start 1.2.3
vim package.json #manually version to 1.2.3
git commit package.json -m "bump version"
git flow release finish 1.2.3
#accept default commit message populated by git flow for merge commit
#type "release v1.2.3" for the tag message
git push origin master --tags #pushes tag named "v1.2.3"
git push origin develop

It involves:

• typing the version number a total of 4 times
• don’t get the version number decided automatically (whether it is a patch or minor)
• don’t get the tag message auto-populated with the commit messages from what has changed since the last release
• have to type many commands

I’m using git flow as a general branching strategy tool, not just for releases, and would like to continue doing so. I would like for git flow to still control the anything to do with branching and committing, and use conventional-changelog for determining what the next version number should be, and auto-populating the tag commit message.

Is there some combination of command line options or configuration that will allow me to achieve this?

Thanks!

[benmarten]

standard version is not at all gitflow compliant

[hutson]

@benmarten would you please consider filing issues with standard-version to bring up each issue that inhibits its use with git flow.