Revolutionize Your Release Management with Git-Tag-Release-Automator!

If you are a friend of git flow and use git tagging in your release flow, I'm sure you struggle with manually determining the latest git tag and then creating a matching release branch is a tedious task. What if there was a way to automate this process to save time, effort and errors?

The "git-tag-release-automator" automates exactly this process and you can concentrate on your real work.

The "git-tag-release-automator" takes care of the following steps for you:

• the last git tag is searched for. If no version tagging is used yet, the "git-tag-release-automator" sets it up for you. You have the choice if your version starts with a "v" or e.g. v1.4.5 or without.
• The "git-tag-release-automator" gives you the possibility to create a new release branch based on the last git tag, e.g. release/v1.4.0.

Initial setup for new projects.

 git-tag-release-automatorThere are no existing tags. Do you want to create a tag starting with 'v'? (y/n)Your choice: yNo "release/v1.0.0" found, create one? (y/n)Your choice: yRelease branch "release/v1.0.0" created.Now you can merge into "release/v1.0.0" and create tags.

Create new tag but there is no matching release branch.

 git-tag-release-automatorLatest tag: v1.4.1Which part of the version do you want to increase: Major (M), minor (m) or patch (p)?Your choice: mNo "release/v1.5.0" found, create one? (y/n)Your choice: yRelease branch "release/v1.5.0" created.Now you can merge into "release/v1.5.0" and create tags.

Create new minor version tag.

 git-tag-release-automatorLatest tag: v1.4.1Which part of the version do you want to increase: Major (M), minor (m) or patch (p)?Your choice: mGit tag v1.5.0 created and pushed successfully.

Create new patch version tag.

 git-tag-release-automatorLatest tag: v1.5.0Which part of the version do you want to increase: Major (M), minor (m) or patch (p)?Your choice: pGit tag v1.5.1 created and pushed successfully.

By automating this process you can save time, nerves and most of all errors and ensure that you always create a consistent git-tag and correct release-branches. You will be sure that your software always has a correct version.

Once you've set up the script, you'll find that not only is it easier to create release branches, but it also leads to a more productive workflow. You can focus on the most important aspects of your project and rely on the script to do the rest.

*Download here: *git-tag-release-automator