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

GIT_PUSH_CERT* env vars and update/post-update hooks...

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Dec 24, 2014, 01:57 UTC
Message-ID
<549A1D8A.3020106@gmail.com>
Hi git core devs,

Any chance I could persuade you to set the GIT_PUSH_CERT* environment variables for the update (and post-update) hooks also?

Background: gitolite "takes over" the update hook [1] for authorisation
and enforcement, and I want to avoid taking over the pre-receive hook
also in order to do this check.

The post-update is not so important; gitolite doesn't use it anyway, so if I have to take over one of them, I may as well take over post-receive. I just added that for consistency.

thanks sitaram

[1]: because it's nice to *selectively* reject refs when more than one ref is pushed at the same time; pre-receive is "all or none".

Next: Junio C Hamano
Message 1 of 2 in “GIT_PUSH_CERT* env vars and update/post-update hooks...”
  1. Sitaram ChamartyDec 24, 2014
  2. Junio C HamanoDec 29, 2014

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.