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.

  • how can I list all the different versions of a file, and diff them also?
  • How can multiple people contribute to resolving conflicts during a large DVCS rebase operation?
  • Git rebase continually fails and requires manual merge intervention
  • How to show diff of changes made in a merge commit?
  • git-svn: reset tracking for master
  • Jenkins doesn't fetch the correct Gerrit branch
  • Teamcity after git force push
  • how to host gem in Github and use it?
  • Why does a “git push” just hang there indefinitely using MySysGit 1.7.4?
  • Heroku Error H10 (App crashed)
  • How to properly rebase in SourceTree?
  • Does Git delete empty folders?
  • 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.