| Issue 577: | Implement gitolite style private branches | |
| 5 people starred this issue and may be notified of changes. | Back to list |
The following description is copied from http://progit.org/book/ch4- 8.html#personal_branches A lot of code exchange in the git world happens by “please pull” requests. In a corporate environment, however, unauthenticated access is a no-no, and a developer workstation cannot do authentication, so you have to push to the central server and ask someone to pull from there. This would normally cause the same branch name clutter as in a centralised VCS, plus setting up permissions for this becomes a chore for the admin. Gitolite lets you define a “personal” or “scratch” namespace prefix for each developer (for example, refs/personal/<devname>/*), with full permissions for that dev only, and read access for everyone else. Just choose a verbose install and set the $PERSONAL variable in the “rc” file to refs/personal. That’s all; it’s pretty much fire and forget as far as the admin is concerned, even if there is constant churn in the project team composition.
Jul 9, 2010
I am taking the approach of adding a ${user} variable to the interpretation of refs. This variable will be interpreted as the value of the current username. This allows rules to be added which give users branch permissions depending on their username. An example might be /refs/heads/${user}
Jul 15, 2010
Fixed by Ib8692a13221a4581731e753e9c7cccb7aa0a96da
Status:
Fixed
Labels: -Milestone-2.1.4 FixedIn-2.1.4
Mar 27, 2012
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |
Owner: mf...@codeaurora.org
Labels: Milestone-2.1.4