Why not use a post-receive hook on github instead? Then it gets called any time you push changes, instead of you trying to remember to install your hook after every clone. --tek
On Tue, Sep 9, 2008 at 1:53 PM, Bill Burcham <[EMAIL PROTECTED]> wrote: > > I've got a post-commit hook that I'd like to have in place for every > clone I make of repository A. (Imagine that I'm managing tickets for > project A on Lighthouse). > > What's the cleanest way to do that? I see these alternatives: > > 1. keep a copy of the post-commit hook file in a handy place and > manually copy it in after each clone (hope I don't forget!) > 2. redefine git clone on my system (using alias_method_chain ;-) to > copy over that file after each clone. Um, the script will need to look > at the repository URL and decide whether I need the hook or not > > Then there's the question of how to do this for everybody on the > project. What are your best-practices? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
