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 have a repo that I need to use to deploy the production code of an WebApp to the server. I need advise on what is the correct way of doing it(branching).
I will need 3 branches(I think):
- Development
- Quality
- Production
Now my doubt is… the “master” branch should be used to the Development or to the Production code?
Best Regards,
Leave the master branch as your main channel, or a preserved state of the working code. That way, if something goes really, really wrong, you can revert back to the master branch. If you’re working with an open source project, put the vanilla engine in the master and branch off of that – it will make updating easier in the future.
I’d say keep the branches like they are right now, and sync the servers with their specific branches. That way you can easily merge, push, and pull to your respective servers. That’s how my workflow is, using git-hooks to automatically sync the branches.