Hosting git repositories -- Gitolite allows you to setup git hosting on a central server, with very fine-grained access control and many (many!) more powerful features.
Find a file
2012-03-25 12:24:12 +05:30
conf clean up gl-system-install 2012-02-22 06:25:22 +05:30
contrib fork ADC: stop carrying along non-gitolite hooks 2012-02-29 13:23:58 +05:30
doc specify documentation licensing as CC-BY-NC-SA 2012-03-02 10:08:18 +05:30
hooks 3 new VREFs plus doc 2012-02-26 19:27:33 +05:30
src mirroring: fix several minor issues related to 'reponame.git' 2012-03-24 16:15:33 +05:30
t (minor fixups related to virtual ref) 2012-02-26 19:33:26 +05:30
.gitattributes docs and .gitattributes hadn't been updated for the change in hooks dir 2010-03-10 06:24:53 +05:30
.gitignore add conf/VERSION to .gitignore 2010-03-02 05:39:19 +05:30
Makefile next round of doc changes 2012-02-24 12:47:28 +05:30
README.mkd mention g3 in README 2012-03-25 12:24:12 +05:30

Gitolite README

2012-03-25: there is a completely re-written version of gitolite in the "g3" branch. The old version will now be supported only for existing users, and for people who need the features that have not yet made it to the new one. To reflect this, the pu branch has been merged into master and deleted.

The steps to use the new version are:

git clone git://github.com/sitaramc/gitolite
cd gitolite
git checkout g3

Documentation is currently available at g3di


Github users: please read the "wiki" link at the top of the page before submitting issues or pull requests.

If you're really impatient, and you're familiar with Unix and ssh, follow the quick install instructions.

But if you want to do anything meaningful with gitolite you have to spend some time cuddling up to the docs. The complete online documentation starts here -- this is the best starting point for general questions about git, such as what it is, why you would need it, features, contact/mailing list info, and so on.

For convenience, here is a link to the master table of contents, which is very useful to search using your browser's search function.


License information for code and documentation is at the end of doc/index.mkd (or you can read it online [here][license]).