Menu
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.
306
The difference between tags and branches are that a branch always points to the top of a development line and will change when a new commit is pushed whereas a tag will not change. Thus tags are more useful to "tag" a specific version and the tag will then always stay on that version and usually not be changed.
Use the “git flow release start” command to create the release branch. When the release is stable, run the “git flow release finish” command. $ git flow release finish '0.1. 0' Already on 'master' Deleted branch release/0.1.
Git-flow is a wrapper around Git. The git flow init command is an extension of the default git init command and doesn't change anything in your repository other than creating branches for you.
The Gitflow Workflow defines a strict branching model designed around the project release. This workflow doesn't add any new concepts or commands beyond what's required for the Feature Branch Workflow. Instead, it assigns very specific roles to different branches and defines how and when they should interact.
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.
HTH
193
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
