githooks

Is there a difference between pre-push and pre-receive hook in git, in terms of use case or working logic? The only difference I could understand from their documentation was in terms of the input they receive - 1. Pre-Push : Information about what is to be pushed is provided on the hook's standard input with lines of the form - local ref SP local sha1 SP remote ref SP remote sha1 LF 2. Pre-receive : For each ref to be updated it receives on standard input a line of the format - old-value SP new-value SP ref-name LF However, I would like to know if there are particular use cases for each hook

I'm kinda new to git. Also, this is my first project where I'm automating the deployment process. So far it's been bliss to being able to do git push dev and have files uploaded, config files copied, etc. Now I want to minify JS/CSS files when I push to my dev server. I was thinking of installing some command-line tool on the server for minifying and for-each js/css file on certain folder, compress and save, on a post-receive git hook. Is this a good approach? (cause I've read about adding compressed files to the repo and other ideas I don't feel quite convinced) If so, which tools are best

I'm trying to setup a git hook that will disallow anyone to delete the master, alpha, and beta branches of our repository. Can anyone help with this? I have never done a git hook so i don't want to try my luck in developing my own without a little help. Thanks in advance. Straightforward with a pre-receive hook. Assuming you're using a bare central repository, place the following code in your-repo.git/hooks/pre-receive , and don't forget to chmod +x your-repo.git/hooks/pre-receive . #! /usr/bin/perl # create: 00000... 51b8d... refs/heads/topic/gbacon # delete: 51b8d... 00000... refs/heads

I have a Git pre-commit hook that prevents me from committing to master unless overridden, in order to encourage developing on branch. However I would like to automatically allow merge commits to master. Is there a way to identify a merge commit from my pre-commit hook script? The script looks like this: #!/bin/bash BRANCH=`git branch --color=never| grep '^*'|cut -c3-` if [ "${BRANCH}D" == "masterD" -a "${GIT_COMMIT_TO_MASTER}D" != "trueD" ] then echo "Commit directly to master is discouraged." echo "If you want to do this, please set GIT_COMMIT_TO_MASTER=true and then commit." exit 1 fi

Is there a way to hook when a git pull happens on the remote (similar to a pre-receive or post-receive). Basically I'd like to be able to cause the remote to commit whatever it has when there is a pull. In my situation, whatever is live on the remote is an authoritative source which may get modified without a git commit. I want to make sure when I pull I'm always able to get the latest of whatever is live. First, to answer your actual question: there are no hooks invoked on the remote side when someone fetches. (When someone pulls, all the remote knows is that they fetched from it - it doesn't

With Github one can write a well-formatted README.md file and document to present the project. Also, there are wiki pages for user to collaborate. I'm wandering what would be an optimal workflow, even for non tech users, to make use of the GitHub platform to write a collaborative book. How to use markdown but then enhance it by applying a stylesheet, make PDF out of it, organise chapters, have a public site (gh-pages) out of it and so on? Is there such a project or tool chain for GitHub? In other word, how to easily write a collaborative book with a nice html and PDF output in GitHub? Thanks.