# global hooks 6 messages from 2008-03-19 to 2008-03-20. Participants: Victor Bogado da Silva Lins, Jonathan del Strother, Junio C Hamano, Johan Herland, Ping Yin. Thread: https://gitlist.dev/t/12764 ## Victor Bogado da Silva Lins, 2008-03-19 16:04 Subject: global hooks Message-ID: <1205942671.691.8.camel@omicron.ep.petrobras.com.br> URL: https://gitlist.dev/e/1205942671.691.8.camel%40omicron.ep.petrobras.com.br ``` Hi, I made a prepare-commit-msg hook today, it basically appends the diff I am about to commit to the commented information that normally appears. The problem is that if I want this hook in all projects I have, I have to copy that file to every single project I have. This is an error prone operation, not to mention a pain in the... . SO my question is, is there a way to make that hook global to all projects? If not, would it be a good idea to allow this? ``` ## Jonathan del Strother, 2008-03-20 01:04 Subject: Re: global hooks Message-ID: <57518fd10803191804g7b2ce670xe5d89b53c1bb8f6f@mail.gmail.com> URL: https://gitlist.dev/e/57518fd10803191804g7b2ce670xe5d89b53c1bb8f6f%40mail.gmail.com In-Reply-To: <1205942671.691.8.camel@omicron.ep.petrobras.com.br> ``` On Wed, Mar 19, 2008 at 4:04 PM, Victor Bogado da Silva Lins wrote: > Hi, I made a prepare-commit-msg hook today, it basically appends the > diff I am about to commit to the commented information that normally > appears. > > The problem is that if I want this hook in all projects I have, I have > to copy that file to every single project I have. This is an error prone > operation, not to mention a pain in the... . > > SO my question is, is there a way to make that hook global to all > projects? If not, would it be a good idea to allow this? I'd love to see something along these lines - at the moment, I have a precommit hook to drop textmate's caret metadata from the commit file, and it's a pain having to symlink it into every git repo. ``` ## Junio C Hamano, 2008-03-20 02:25 Subject: Re: global hooks Message-ID: <7vk5jyyvw1.fsf@gitster.siamese.dyndns.org> URL: https://gitlist.dev/e/7vk5jyyvw1.fsf%40gitster.siamese.dyndns.org In-Reply-To: <1205942671.691.8.camel@omicron.ep.petrobras.com.br> ``` Victor Bogado da Silva Lins writes: > SO my question is, is there a way to make that hook global to all > projects? If not, would it be a good idea to allow this? Probably a post- git-init hook that lets you do anything to your newly created repository would be the only thing that you need. Then you can copy, untar or even use symlink to muck with .git/hooks/ in whatever way you please. There needs a mechanism for you to specify what that hook is, and it cannot be in individual repositories, so it has to live in ~/.gitconfig somewhere. ``` ## Johan Herland, 2008-03-20 11:20 Subject: Re: global hooks Message-ID: <200803201220.47503.johan@herland.net> URL: https://gitlist.dev/e/200803201220.47503.johan%40herland.net In-Reply-To: <7vk5jyyvw1.fsf@gitster.siamese.dyndns.org> ``` On Thursday 20 March 2008, Junio C Hamano wrote: > Victor Bogado da Silva Lins writes: > > > SO my question is, is there a way to make that hook global to all > > projects? If not, would it be a good idea to allow this? > > Probably a post- git-init hook that lets you do anything to your newly > created repository would be the only thing that you need. Then you can > copy, untar or even use symlink to muck with .git/hooks/ in whatever way > you please. > > There needs a mechanism for you to specify what that hook is, and it > cannot be in individual repositories, so it has to live in ~/.gitconfig > somewhere. Or you could add the hook (either the post-init hook, or for that matter the hook you want to make global) to the Git template directory on your system (/usr/share/git-core/templates by default). If you don't want to make it system-global (only user-global), I guess you could make your own Git template directory somewhere (copy the system's template dir, and add/enable whatever hooks you like), and set up an alias to "git init --template=". Then use this alias instead of "git init". ...Johan -- Johan Herland, www.herland.net ``` ## Ping Yin, 2008-03-20 12:26 Subject: Re: global hooks Message-ID: <46dff0320803200526x7b2a535fu25bae005348bb8e6@mail.gmail.com> URL: https://gitlist.dev/e/46dff0320803200526x7b2a535fu25bae005348bb8e6%40mail.gmail.com In-Reply-To: <200803201220.47503.johan@herland.net> ``` On Thu, Mar 20, 2008 at 7:20 PM, Johan Herland wrote: > On Thursday 20 March 2008, Junio C Hamano wrote: > > Victor Bogado da Silva Lins writes: > > > > > SO my question is, is there a way to make that hook global to all > > > projects? If not, would it be a good idea to allow this? > > > > Probably a post- git-init hook that lets you do anything to your newly > > created repository would be the only thing that you need. Then you can > > copy, untar or even use symlink to muck with .git/hooks/ in whatever way > > you please. > > > > There needs a mechanism for you to specify what that hook is, and it > > cannot be in individual repositories, so it has to live in ~/.gitconfig > > somewhere. > > Or you could add the hook (either the post-init hook, or for that matter > the hook you want to make global) to the Git template directory on your > system (/usr/share/git-core/templates by default). If you don't want to > make it system-global (only user-global), I guess you could make your > own Git template directory somewhere (copy the system's template dir, > and add/enable whatever hooks you like), and set up an alias to > "git init --template=". Then use this alias instead > of "git init". > template dir is meaningful for static hooks. However, sometimes we need dynamic hooks which change over time. Having a real global hook can help to implement a single logic or policy spreading among multiple repositories. For example, we can enfore a policy to help to update the test or deploy environent automatically: when repositories are pushed into a central place, they are checked out into different places or hosts automatically. I think ~/.gitconfig is a good place to give such an entry point. -- Ping Yin ``` ## Johan Herland, 2008-03-20 12:56 Subject: Re: global hooks Message-ID: <200803201356.16512.johan@herland.net> URL: https://gitlist.dev/e/200803201356.16512.johan%40herland.net In-Reply-To: <46dff0320803200526x7b2a535fu25bae005348bb8e6@mail.gmail.com> ``` On Thursday 20 March 2008, Ping Yin wrote: > On Thu, Mar 20, 2008 at 7:20 PM, Johan Herland wrote: > > On Thursday 20 March 2008, Junio C Hamano wrote: > > > Victor Bogado da Silva Lins writes: > > > > SO my question is, is there a way to make that hook global to all > > > > projects? If not, would it be a good idea to allow this? > > > > > > Probably a post- git-init hook that lets you do anything to your newly > > > created repository would be the only thing that you need. Then you can > > > copy, untar or even use symlink to muck with .git/hooks/ in whatever way > > > you please. > > > > > > There needs a mechanism for you to specify what that hook is, and it > > > cannot be in individual repositories, so it has to live in ~/.gitconfig > > > somewhere. > > > > Or you could add the hook (either the post-init hook, or for that matter > > the hook you want to make global) to the Git template directory on your > > system (/usr/share/git-core/templates by default). If you don't want to > > make it system-global (only user-global), I guess you could make your > > own Git template directory somewhere (copy the system's template dir, > > and add/enable whatever hooks you like), and set up an alias to > > "git init --template=". Then use this alias instead > > of "git init". > > template dir is meaningful for static hooks. However, sometimes we > need dynamic hooks which change over time. Having a real global hook > can help to implement a single logic or policy spreading among > multiple repositories. If you need to centralize the logic, you can just keep the actual hook outside the template directory, and store an (absolute) symlink within the template dir pointing to the hook. All your git repos will now exercise the centralized hook instead of each having a separate copy. > For example, we can enfore a policy to help to update the test or > deploy environent automatically: when repositories are pushed into a > central place, they are checked out into different places or hosts > automatically. > > I think ~/.gitconfig is a good place to give such an entry point. Still, I think this can be solved with the existing tools, without adding more features and config directives. ...Johan -- Johan Herland, www.herland.net ```