Giving users their own branches
When there are more than a few developers in a project, it is often necessary for them to share code that is still under development, for comments, discussion, preliminary testing, and so on. The obvious solution is for each developer to push to a branch on the Gitolite server and inform his colleagues of the branch name. A branch namespace dedicated to this can be created, giving all developers access to it, as follows:
repo foo RW+ sandbox/ = @developers
This works fine, but it could lead to a situation where one developer accidentally overwrites or deletes another developer's branch if the branch naming within the sandbox namespace is not strictly controlled.
What is required, ideally, is something as follows: ...
Get Gitolite Essentials now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
