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.
Git noob here.
I know this is against the principal of “distributed source control” but I want to “password protect” certain development branches in my GIT repository. That is, I don’t want that branch to be available via git branch -r, except to a certain group of developers who need access to that branch, via some sort of password.
Possible?
You can have a separate repository cloned from the public one with its own branches.
This repository could be in the filesystem with the right ACLs or group permissions, or it could be a separate server requiring proper login credentials, etc. Then developers could commit, pull, merge, etc. as authorized.