Value and usage of Git-Flow's tag-prefix feature?

I’ve been using git-flow for a while but I still don’t understand the Tag Prefix feature. I assume it’s just a string that prefixes every release/ tag. Does anyone have any usage examples or benefits of doing this? I’ve yet to see any explanation of it in any of the Git Flow blog posts.

  • Validation of variation to Gitflow workflow
  • How to push the “develop” branch to the remote “origin”?
  • Switch branches without losing uncommitted work
  • Git flow: Best practice for dealing with minor releases
  • How to merge a branch to master without taking features that aren't production ready?
  • How should I update the version inside my pom.xml when releasing using git flow?
  • Multiple features for one branch - what's the point?
  • Start new feature with existing name using Smartgit
  • One Solution collect form web for “Value and usage of Git-Flow's tag-prefix feature?”

    We use it to help with identifying the build that is in each of our environments. Our release tag prefix is “stage-“.

    We name our releases with a date stamp – “041912” When we do a “git flow release start 041912” a branch will be created called stage-041912 and we bump the version number to that tag name (trying to automate this – see my latest question that I posted) in the footer. Our QA team looks here to ID the version that they are using when they are writing tickets in our issue tracker.

    This has worked very well for us in our release workflow.


    Git Baby is a git and github fan, let's start git clone.