git-post-receive

We're using git with a central repo (using Gitosis). I've created a post-receive hook to generate an email to the dev mailing list whenever changes are pushed to the central repo, and to generate documentation from the documentation folder in the git repo. Therefore, in ~git/ I've got a directory, we'll call it 'a' that contains a clone of the git repo. The post-receive hook looks like: #!/bin/bash cd ~git/repositories/a.git . ~git/post-receive-email &> /dev/null ( cd ~git/a && git pull &> ~git/pull_log.log && php ~git/a/scripts/generate_markdown_documentation.php &> ~git/doc_log.log ) The

In a team we have a gitlab set up that is avialable only to our team and is meant for development purposes, pushing, branching etc and we have an official git repo to which we would like to mirror commits only from master branch (stable). I know that this can be done with use of server-side git hooks but how specifically can I do that so that the developers won't have to type anything extra and the hook will be set on gitlab (no on developers' machines - local repos) ? Take a look at this recipe . In the recipe the author propagates changes being pushed to the master to a working tree, you

I'm running GitLab v5.2 on the same server as my production webserver (Document Root in /var/www). I'm trying to setup a standard GitLab Post-Receive Hook but am finding surprisingly little information about how to set up a script to process the posted JSON data. I'm not trying to do anything custom, just right out of the box, I want to receive the post-receive data at my website location (remember on the same server), and then pull from origin-master when it gets received (provided the post-receive data originating push was to the master branch). This way, the website found in /var/www is

I am running a web server that allows users to upload images to the server. However, I am using git to manage my source code, and the git push operation deletes anything on the server which doesn't match my local checkout - so I lose the images every time I run git push ! At first I thought that I might be able to protect the uploads folder, so I tried all of these things as suggested in other posts: adding the directory to .gitignore, git rm --cached -r uploads git update-index --assume-unchanged uploads None of these solve the issue - the remote directory always disappears when I do git push

I have a post-receive hook that is running as user 'git'. I have a virtualenv /python/ve//bin/activate that is readable by git. Running: source /python/ve/<name>/bin/activate works fine for a user in the git group. When it runs as a post-receive hook after a push, I get the error "source: not found". I'm not sure where else to look - any hints much appreciated. This is something of a guess, since you haven't quoted your complete post-receive hook, but I suspect that you don't have a shebang line pointing to /bin/bash at the top. Your post-receive hook should begin: #!/bin/bash I suspect this

I have a git post-receive hook that extracts all the revisions that were added during a "git push" and does some processing on each one (such as sending notification emails). This works great except when merging; e.g.: I make some commits on branch1 and then push branch1. The post-receive hook processes the commits correctly. I merge branch1 into branch2 and then push branch2. The post-receive hook processes all the merged commits a second time. How can I avoid this? Below is the beginning of my post-receive hook where I extract the commits that should be processed (at the end $COMMITS holds

I created a bare git repo on my server and set up the following post-receive hook from this blog : #!/bin/bash while read oldrev newrev ref do branch=`echo $ref | cut -d/ -f3` if [ "master" == "$branch" ]; then git --work-tree=/path/to/my/project/live/ checkout -f $branch echo 'Changes pushed live.' fi if [ "develop" == "$branch" ]; then git --work-tree=/path/to/my/project/dev/ checkout -f $branch echo 'Changes pushed to dev.' fi done So that whenever I push locally to my server, the changes would automatically be published on each branch's folder without the need to manually pull. I set the