gitolite

I am trying to enforce a policy where each push gets rejected when even one of the commit messages does not satisfy a rule. I've distributed a hook to the devs in order for them to use it in their local repos but I also want to enforce this when they push to the origin. I have two questions: Should I use the update hook or the pre-receive hook? (I've tried to setup an update.secondary hook but it seems to me it doesn't get fired, while a pre-receive does). How can I get the message for each commit contained in the push? More specifically, I want each commit message to have a specific "valid"

How to configure git and gitolite to allow specific user to change just files that are inside specific directory? e.g. files in origin master branch: /dir1/ /dir2/file1 /dir2/file2 /dir3/file1 User kathrine , allow to change only /dir2/file1 and /dir2/file2 $kathrine: git clone git@example.com:test.git results in: /dir2/file1 /dir2/file2 Are there any per-dir directives in gitolite.conf or shall I configure git with new branch for this user? I just don't want graphics designer to have access to the source code files. 2010: For Gitolite 2 (might have changed for gitolite 3) No (meaning a

I've managed to init an empty git repo on my NAS, and I attempted to add a new user by generating a new public key "foo.pub" and copying + pasting it into keydir/ and committing that and pushing it onto the NAS. First, the files: Here is my ~/.ssh/config file: Host root HostName iptonas User root Port 123 Host foo HostName iptonas User foo Port 123 identityfile ~/.ssh/foo Grabbed a copy of gitolite-admin from NAS: git clone ssh://root/gitolite-admin I get: Cloning into 'gitolite-admin'... remote: Counting objects: 12, done. remote: Compressing objects: 100% (9/9), done. remote: Total 12 (delta

I stuck here now for like 2 Days a week. I've got a CentOs machine with Gitlab4 and gitolite. Everything worked fine for weeks, but suddenly last weekend something strange happend quite all binaries disappeared from the mashine ( like yum, python, ruby, mysql ect. ) i've really no clue how that can happn... After hours of reinstalling and compiling gitlab was working again. But i cant get the ssh keys between the gitlab and git user working. I already deleted and recreated the git user, set again all permissions, recreated the ssh keys, reinstalld gitolite ect. But nothing worked i keep

I'm using post-receive-email hook from the Git distribution to send e-mails to certain users when Git repository is updated (hook invoked from post-receive ). All my repositories were managed manually. Now, I get so many repos and so many users and groups that I have to upgrade to some Git repository management system. I picked Gitolite. But I am a bit at loss on how to configure the e-mail notifications. Update: I will elaborate the question a bit: First question is: Where should I put the hook and should I change it somehow so it would work with Gitolite? Second question: The standard post

Things such as Github, Bitbucket, DropBox -- manages the content-hosting such as tickets and repo -hosting (DB not tickets but can be used to store repos). I want a solution where I manage myself the content-hosting of thing such as Git -repositories and tickets. Trial 0: trying to tune Git, too time-consuming I followed the instructions here but some difficulties then I followed a lot of other tutorials with much more difficulties. I got cloning with "git clone --bare xxx xxx.git; cd xxx; git update-server-info" working but unable to push things with "--shared" , got fed up to this kind of