Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve been using git for about a year and would like to use tagging to, well, tag commits at different versions. I’ve found lots of info on the commands to use to work with tags, but what I’d like to know is why use tagging at all if I can just create a new branch called 1.1.0 and not have to cloud my mind with a whole new set of git commands?
There has to be a lot of good reasons for tagging rather than branching but I’d like to know what those advantages are.
Tags are mainly used for future reference to the specific version of the project, by tagging a commit. You can always use branches of course, but if you change versions a lot, you will end up with lots of unused or rarely used branches.
Practically, tags are branches without branches anyway, just adding a way to reference a specific version of the project to reduce complexity.
Edit: Here is a nice way to use git that I use for all my projects.