git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How-to checkin git hook

From
JDJoe D'Abbraccio <dajoe13@gmail.com>
Date
Aug 17, 2009, 20:46 UTC
Message-ID
<4A89C192.1010205@gmail.com>
In-Reply-To
<81b0412b0908171327l1dd1a36n5e58828d70b18bfe@mail.gmail.com>
Thanks for the info.

How do people typically manage the hooks for their projects? These may change over the life of the project and may be project version dependent. Is the best way to place them into another subdir within your project with instructions on updating the hooks files? Looks like a step that would be prone to errors though.

And how about the fact that post-checkout.sample is missing in the release I am using. Is this the only one missing or are there others?

It would also be a good idea if the githooks man page explains this. Maybe when I better understand how hooks are best managed, I will provide my thoughts on the man page.

Regards, Joe

Alex Riesen wrote:
Show 17 quoted lines
> On Mon, Aug 17, 2009 at 22:15, Joe D'Abbraccio<dajoe13@gmail.com> wrote:
>> I have not been able to find out how to commit and push a hook to my git
>> server archive for everyone's benefit. The githooks man page does not
>> describe this and I have not turned up any fruitful google searches on the
>> topic.
>>
>> I am trying to add a post-checkout hook. I also noticed that the
>> post-checkout sample does not exist when I init a new archive. Is this a
>> bug?  I am running git version 1.6.0.2.
> 
> No. It didn't occurred to anyone before to push repository's configuration
> and service files (the hooks). Everybody just copied them into the server
> repositories or edited them in place.
> 
> If the server is a public place like github, it is not very likely they allow
> you to run anything you like on their servers (and hooks are programs).
> 
Previous: Alex Riesen
Message 4 of 4 in “How-to checkin git hook”
  1. Joe D'AbbraccioAug 17, 2009
  2. Erik Faye-LundAug 17, 2009
  3. Alex RiesenAug 17, 2009
  4. Joe D'AbbraccioAug 17, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.