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

Re: git pre-push hook to restrict master branch push !!!

From
JBJ. Bakshi <joydeep@infoservices.in>
Date
Jun 20, 2012, 12:39 UTC
Message-ID
<20120620180947.755a96ba@shiva.selfip.org>
In-Reply-To
<20120611174757.2f0bdd83@shiva.selfip.org>

On Mon, 11 Jun 2012 17:47:57 +0530 "J. Bakshi" <joydeep.bakshi@infoservices.in> wrote:

Show 30 quoted lines
> On Mon, 11 Jun 2012 17:40:37 +0530
> Sitaram Chamarty <sitaramc@gmail.com> wrote:
> 
> > On Mon, Jun 11, 2012 at 4:48 PM, J. Bakshi
> > <joydeep.bakshi@infoservices.in> wrote:
> > > Hello list,
> > >
> > > I have a central server where git repos are located and based on http base push/pull.
> > > authentication is done by a text based password file, generated by htpasswd.
> > >
> > > I am searching for a server side hook (pre-push) which can prevent all push to master,
> > > except few users found at that password file generated by htpasswd. Is there any such hook
> > > available ? Some suggest to use gitolite, but it also based on the hooks to do the same.
> > 
> > If you don't want to use gitolite, you can roll  your own update hook.
> >  It can be as simple as
> > 
> >   - check $REMOTE_USER to see if the name is in the "allowed" list
> > (your choice how you want to maintain that list).  If allowed, 'exit
> > 0".
> >   - otherwise check $1 (argument 1) to see if it is
> > "refs/heads/master".  If it is, "exit 1".
> > 
> > How difficult is that?
> 
> Thanks for the clue. I'm not familiar with the hook programming.
> I'll check further with the clues you have given.
> 
> -- with regards.
> --

The refs/heads/master checking is fine. Can I placed this checking in my httpd.conf file to check user against a htpasswd file ?

Thanks
Previous: J. Bakshi
Message 4 of 4 in “git pre-push hook to restrict master branch push !!!”
  1. J. BakshiJun 11, 2012
  2. Sitaram ChamartyJun 11, 2012
  3. J. BakshiJun 11, 2012
  4. J. BakshiJun 20, 2012

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.