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.

  • Git repository on S3 (as “origin”, not as backup)
  • How to setup Push/Pull in Git?
  • Does git smartly handle a zip archive in which only one of the files changes regularly?
  • Git status compared to different remote
  • Xcode git not showing xcassets to commit
  • can .ptvs be saftely git ignored?
  • git: create tag and push to remote: why tag is behind master on remote?
  • Denying commits that are not merge commits
  • How to clean up line-endings with Git
  • Collaboration
  • Update git submodules shallowly with the '--depth' option
  • Undo Git Stash Pop with Merge Conflicts and Other Files in Working Directory
  • 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.