gitolite

When I create a new repo on my gitolite repository I always have to enter the following command before I can start pushing code to the server. git push origin master:refs/heads/master What does it do ? My guess is that is has to do with the head reference not sure. Could someone explain it to me? There's three parts to this command: git push This invokes the push command origin This names the remote to which you are pushing. This is either one of the named remotes stored in .git/config (you can list these with git remote ), a URL, or the token . which means the current repository. master:refs

I have set up gitolite hopefully as per the instructions, and everything is working as planned. I am slightly unsure as to how the usernames part works, and looking through the docs hasn't helped me - perhaps I'm missing something simple. If I have two client machines, for use by one real person, but on each of those machines the usernames are, let's say dave and david. How can I organise the keys in keydir and any config file so that they both represent the same user? I get the suffix thing, dave@laptop, dave@desktop (I think), just not how to have different client machine usernames

I'm wondering is there a simple way to install hooks for certain repo using gitolite_admin. Let's imagine i want to have post-update hook for repo awesome using gitolite_admin repo cloned to my workstation... #conf/gitolite_conf repo awesome RW+ = deployer contents of post-update : #!/bin/sh echo "Post receive-hook => updating Redmine repository" sudo -u deployer perl -we '`cd /home/deployer/repo/awesome.git && git fetch -q --all`' sitaram You could also look at " repo-specific environment variables " A special form of the option syntax can be used to set repo-specific environment variables

I've been trying very hard to get gitolite working. I used the package approach and am able to do a first "git push" with a first user to the server. After that, if if I add a key and try to push something again, I get an error saying "W access for gitolite-admin DENIED to mike"- note that it's supposed to be using the gitolite user- not my username. I guess this is because I'm adding private keys for both users in my .bash_profile. (I'm using msysgit)... Any ideas? Thanks a lot! VonC I guess this is because I'm adding private keys for both users True, you should use a dedicated public/private

When using git, git ls-remote returns status code 128 while any other commands work flawlessly (push/pull/clone/etc). My repos are being managed with gitolite. I'm getting this error when trying to deploy rails app for the first time. When invoking said command by hand I get standard error like this: fatal: The remote end hung up unexpectedly If this was permissions/public key issue, I wouldn't be able to push/pull to/from the repo. Why does single ls-remote command fail? I figured it out. The problem was in repo's address. I have used git://host/repo address instead of git@host:repo . The

For example: I have a repository - repo1 with such fs hierarchy repo1: js html php/core php/menu And I want to give to repo1:php/menu , RW permission - to a freelancer, but for all repo1 - this freelancer must have only Read-Only permission. Can I do this with gitolite or gitosis or may be something else? VonC The repo access rights on a DVCS is always linked to the all repo, not part of if, mainly because you clone all of it ( shallow clone is hard ). That means gitolite (I won't even mention gitosis which is obsolete) can establish restrictions on: accessing a all repo writing only certain

I've got a server with Gitolite installed to host my repos I created a new repo yesterday and today when I tried to push more commits to the server I am getting: fatal: object 86eeaa0c5a154ff3df34d6a43669930b9c6c7f59 is corrupted error: unpack failed: unpack-objects abnormal exit error: failed to push some refs to As the repo is pretty new I wasn't too bothered about losing previous commits so I have deleted both my local and remote repo but still getting the same error. As I say I'm not too concerned about maintaing my commit history, I would just like to get it working again! VonC As seen in

Consider the following repo: REPO/src/A/ REPO/src/B/ Is it possible by having only 1 repo to implement the following restrictions? On master branch, allow full access to maintainers role On master branch, disallow access to A but allow for B to contributors role. On personal branches, allow full access to A and B to creators. VonC With Gitolite V3 or 'g3' and its VREF , it should be possible to implement those restrictions. But the access you can manage is only for write-access. If a user can clone a repo, he/she will have read-access to all the repo (as mentioned in " gitolite: allow to

I am newby with gitolite. I've install gitolite on a remote server. http://dev.remoteserver.com So I could git-cloning gitolite-admin.git. git clone ssh://gitolite@dev.remoteserver.com/gitolite-admin.git I wanted to add user and repo using gitolite. following is ordinary add user process. In the local repository, conf / keydir directory exists. open conf/gitolite.conf added below text. repo aproject RW+ = testid and, in local-mac, ssh-keygen -t rsa. added the public key in keydir/testid.pub and then, git add / git commit / git push is done well. okay, then I tried to cloning the fresh git repo