deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

progit doc...

Browse source 
thanks to tsgarp for making me think about adding this caution
This commit is contained in:
Sitaram Chamarty 2010-10-04 19:28:33 +05:30
parent b851011ce5
commit dc62d69848
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/progit-article.mkd
View file

@ -1,5 +1,9 @@
## Gitolite ##
Note: the latest copy of this section of the ProGit book is always available within the [gitolite documentation][gldpg]. The author would also like to humbly state that, while this section is accurate, and *can* (and often *has*) been used to install gitolite without reading any other documentation, it is of necessity not complete, and cannot completely replace the enormous amount of documentation that gitolite comes with.
[gldpg]: http://github.com/sitaramc/gitolite/blob/pu/doc/progit-article.mkd
Git has started to become very popular in corporate environments, which tend to have some additional requirements in terms of access control. Gitolite was originally created to help with those requirements, but it turns out that it's equally useful in the open source world: the Fedora Project controls access to their package management repositories (over 10,000 of them!) using gitolite, and this is probably the largest gitolite installation anywhere too.
Gitolite allows you to specify permissions not just by repository, but also by branch or tag names within each repository. That is, you can specify that certain people (or groups of people) can only push certain "refs" (branches or tags) but not others.