githooks

问题 I'm writing a git pre-receive hook on the remote repo to make sure pushed code is consistent with our company's internal guidelines. I'm able to find all the files that are to be checked when a pre-receive hook is fired, however, I don't have the path to these files to open them using normal file operations(e.g. cat git_working_directory/file_name would throw No such file or directory error). The application which validates the code requires the file path as an argument so that it can open

问题 In a project where for instance a parser is involved, some source code is the product of a program. For instance yacc generates - based on a .yy file - a source code file that implements the parser. Since small modifications in the .yy file can lead to large changes in the corresponding source code file after compilation and since the resulting source code is (almost) never altered after it is generated. Such source code files are perfect candidates for the .gitignore list. Now one can of

问题 I am making changes to a project in a branch that, so far, is known to no one else but me. However, starting recently, when I git push to this project, I now receive this as part of the response: remote: Create pull request for <<my branch>>: remote: https://bitbucket.org/... I have no idea why Git is giving me this message, which I have never seen before. Even if I delete the remote branch (with " git push origin :<<my branch>> " I now still get this message! (I successfully deleted the

问题 I have a remote repository for a website which I am developing on my local machine. I use git flow for neat branching model, so my branches are: master develop feature/one feature/two release/one release/two etc The simplified work flow is as follows: make changes in develop push develop to backup server checkout to master merge master with develop` push master to live server What I want to achieve, is that when I push master branch to live server, I should be able to instantly see changes

问题 I have gitosis setup on my server and I'm trying to create a post-receive hook that will checkout changes to a working directory on the remote machine. Initially I got an error saying cannot open /home/user/source/testing-local/.git/FETCH_HEAD: Permission denied so I changed the group ownership of the working directory's .git folder to the git user. Following this I got the error Host key verification failed which led me to check which user was running the hook, git of course (silly me!), so

问题 I have a central git repo set up using gitolite. I want to set up a hook such that whenever a user pushes to the repo, it performs a pull elsewhere followed by some automated testing. So far, I only want to it perform the pull. In the hooks directory I created the following script names post-update: #!/bin/sh cd /home/git/www/epicac git pull When I invoke this script using ./post-update, it does exactly what I want. However, whenever it's invoked automatically as I hook, I get: fatal: Not a

问题 Is there a way to track git hook changes? I have three hooks that only show up on my machine, not when my other developers fetch. Trying to git add doesn't work. 回答1: http://benjamin-meyer.blogspot.com/2008/10/git-hooks.html Files in the .git/hooks directory are not part of the repository and so they are not tracked. A workaround is to have a git_hooks directory at the top of your repository like done in Arora and symlink .git/hooks to git_hooks whenever you clone. This way the hooks will be

问题 Is there a way to track git hook changes? I have three hooks that only show up on my machine, not when my other developers fetch. Trying to git add doesn't work. 回答1: http://benjamin-meyer.blogspot.com/2008/10/git-hooks.html Files in the .git/hooks directory are not part of the repository and so they are not tracked. A workaround is to have a git_hooks directory at the top of your repository like done in Arora and symlink .git/hooks to git_hooks whenever you clone. This way the hooks will be

问题 Not sure if this is possible in git (I haven't found it but I may be using the wrong vocabulary in my searches), but it be would useful to be able to modify and enable hooks as the defaults for all new repositories (at the time of creation I mean) so these don't have to be customized each time a new repository is created. It seems the easy way to do this is write a wrapper that sets my hooks and chmods them when I create a new repository, but if there's a way built into git I would rather use

问题 Not sure if this is possible in git (I haven't found it but I may be using the wrong vocabulary in my searches), but it be would useful to be able to modify and enable hooks as the defaults for all new repositories (at the time of creation I mean) so these don't have to be customized each time a new repository is created. It seems the easy way to do this is write a wrapper that sets my hooks and chmods them when I create a new repository, but if there's a way built into git I would rather use