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.

  • TFS build definition associated commits
  • Version control for prose
  • Git: Two projects, each in a repo. Combine in new repo in sub-dirs with a single linear history
  • Delete multiple repositories at once in Atlassian Stash
  • GIT: Whats the Difference between a Pull Request and a Merge?
  • Visual Studio Solution from multiple git repositories
  • In my repo, how long must the longest hash prefix be to prevent any overlap?
  • git rebase --continue: how to suppress the “no changes” check
  • Git .git/info/refs not valid: is this a git repository?
  • GIT: forgot to commit and have made new changes. How to undo new changes, commit then redo changes?
  • Git - how to recover from a missing blob
  • How can I synchronize project dependencies between developers?
  • 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.