aboutsummaryrefslogtreecommitdiff
path: root/contrib/pre-commit
diff options
context:
space:
mode:
authorBenjamin C Meyer <ben@meyerhome.net>2013-11-06 21:12:26 -0500
committerBenjamin C Meyer <ben@meyerhome.net>2013-11-06 21:51:19 -0500
commit4919c9095d322b2166d3200981dc5c4c2d64eeef (patch)
tree339e8101c4313af3744cd4b9e38fd8f0eb2251a5 /contrib/pre-commit
parenta7b60551d2fb4ce663f0b4fbc9b762c78c03cc8a (diff)
downloadgit-hooks-4919c9095d322b2166d3200981dc5c4c2d64eeef.tar.gz
git-hooks-4919c9095d322b2166d3200981dc5c4c2d64eeef.tar.bz2
Add the ability to remind users when committing to any repo without git-hooks.
It is easy to forget to install git-hooks in a repository you are using. A commit with no error message could both mean you don't have git-hooks installed and it can mean that you do have it installed, but your commit was perfect and there was no errors. The new option --installglobal creates a default .git template that is used by all future cloned repositories (and git init'd) that remind users that the repository doesn't have git-hooks installed. A number of projects I have been involved with used git-hooks, but founds its weakest point was that eventually someone would re-clone a repo and make commits with errors before turning git-hooks back on. Another common problem was when we had multiple git repositories and git-hooks was only installed in some of them, but not all While it would be nice to be able to use --instalglobal to automatically turn on git-hooks on every future repo eventually some git repository on github would include a hook that would email <secret stuff> back home and all you would have to do would be to clone it to activate it which would be a "bad thing", but it can pester you without harm. Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
Diffstat (limited to 'contrib/pre-commit')
0 files changed, 0 insertions, 0 deletions