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.
Let’s say I have two local branches: master & dev. I want to force all pushes on the master branch to a repo called master and all pushes on dev to different one called dev.
Why? Because I want to maintain two continuous integration environments, one for each repo.
What I really want to do is make sure the master repo rejects all branches other than master and vice-versa. It’s fundamental that I don’t inadvertently push the wrong branch to the wrong repo.
Any ideas?
Use
to define the default upstream location.
This will not fully guard you but if you use “push” without parameter it should go to the right remote branch.
Avoid pushing with “+” or –force could help too. If the server uses something like gitolite do not grant the “+” privilege to you user. This would deny non fast-forward pushes.