gitflow-easyrelease aims to streamline git flow release commands. It adds some semver shortcuts as well.

$ pip install --user gitflow-easyrelease

$ export PATH=~/.local/bin:$PATH
$ which git-easyrelease
~/.local/bin/git-easyrelease
$ git easyrelease
< should print the main help >
$ git easyrelease --all-help
< dumps all the help >

version can be one of the following:

• p, patch, or ~ for a patch bump
• m, minor, or ^ for a minor bump
• M or major for a major bump
• X.Y.Z for a new, unconnected semver version
• <any string> for a not semver version

base is an optional branch to use as the base for the release. It requires the extended gitflow-avh_, but it's totally optional and shouldn't break anything if you both don't have gitflow-avh and never use base.

git easyrelease init [base]

Convenience method to seed the release with 0.0.0. It runs

$ git flow release start 0.0.0 <base>
$ git flow release finish

git easyrelease quick version [base]

Convenience method to start and finish a release branch. It runs

$ git flow release start <version> <base>
$ git flow release finish

git easyrelease start version [base]

Extends git flow release start with extra semver functionality. It runs

$ git flow release start <version> <base>

git easyrelease finish [version]

Extends git flow release finish with extra semver functionality. Without version, it attempts to finish the active branch. It runs

$ git flow release finish <version>

git easyrelease publish [version]

Extends git flow release publish with extra semver functionality. Without version, it attempts to publish the active branch. It runs

$ git flow release publish <version>

git easyrelease delete [version]

Extends git flow release delete with extra semver functionality. Without version, it attempts to delete the active branch. It runs

$ git flow release delete <version>

These percentages are pretty arbitrary. Today's 47% could be tomorrow's 90% or vice versa.

Once all of these are finished, I'll release v1. Until then, v0 should be used with caution, because it's not stable.

These are things I'd like to add, but probably won't be included in v1. If not, they'll most likely constitute one or more minor version increments.