tag good pratice #21712
-
Hello everyone, i’m a fullstack developper working for a compagny which passed all their projects Svn into Git two or three years ago. We are doing our best to work thank to the gitFlow. I have a big issue which confusing me, the tech-leads expecting us to tag branches wich are not MASTER in order to deploy them in the production then doing a rebase . As far as I know regarding to the git and gitFlow documentations the one branch we should tag is MASTER. I can make a mistake so I’ll be more then thankfull from you guys to give me returns. Regards |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Hi @joe97228, Welcome to the Github Community Forum! Yes, you are totally right. You can let read this post to your tech-leads: a successful git branching model -Gabriele- Mark helpfull posts with Accept as Solution to help other users locate important info. Don’t forget to give Kudos for great contents! |
Beta Was this translation helpful? Give feedback.
-
thank you @wabri :slight_smile: |
Beta Was this translation helpful? Give feedback.
-
Hi @joe97228 You can actually tag any branch in Git and GitHub. A tag is simply a pointer to a commit. Fun fact: a branch is also just a pointer to a commit. In the case of a branch, it is a pointer to the most recent commit in a line of work. In the case of a tag, it is a pointer to a specific point in time. With regards to what your tech-leads are asking - deploying from something other than master is pretty common. For example, at GitHub we actually deploy from the feature branch and then merge the branch to master. For a really interesting read on how we do it, check out this post: https://github.blog/2015-06-02-deploying-branches-to-github-com/ |
Beta Was this translation helpful? Give feedback.
-
The question is not if it is possible, but if is the right method to version. Is obvious that you can tag every branch. Is like create a new branch, you can create everywhere without problems. The good conduct is to use the master only for tag a new version, git workflow is this. If Github follow another workflow to version is another question.
Thanks a lot to share this blog post :slight_smile: -Gabriele- Mark helpfull posts with Accept as Solution to help other users locate important info. Don’t forget to give Kudos for great contents! |
Beta Was this translation helpful? Give feedback.
-
Hello @joe97228 , This post was moved to a different board that fits your topic of discussion a bit better. This means you’ll get better engagement on your post, and it keeps our Community organized so users can more easily find information. As you’ll notice, your Topic is now in the How to use Git and Github board. No action is needed on your part; you can continue the conversation as normal here. Let me know if you have any other questions or if I can help with anything else. Greatly appreciated, -MChevy422 |
Beta Was this translation helpful? Give feedback.
Hi @joe97228,
Welcome to the Github Community Forum!
Yes, you are totally right.
You can let read this post to your tech-leads: a successful git branching model
-Gabriele-
Mark helpfull posts with Accept as Solution to help other users locate important info. Don’t forget to give Kudos for great contents!