From: Andreas Ericsson <ae@op5.se>
To: Ishaaq Chandy <ishaaq@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: disable branch modification
Date: Tue, 04 Aug 2009 15:36:43 +0200 [thread overview]
Message-ID: <4A78396B.70004@op5.se> (raw)
In-Reply-To: <24550469.post@talk.nabble.com>
Ishaaq Chandy wrote:
> Hi all,
> I've got a remote git repository that I want multiple users to be able to
> push to. This is all set up fine and working beautifully. The only thing is,
> I want to be able to lock down the branches on this remote repo, once set up
> users should not be able to:
>
> 1. Create new branches on it
> 2. Delete existing branches from it
> 3. push non-fast-forward commits to it.
>
> I think I'll need to write a pre-receive hook for this, but before I embark
> on this, any helpful pointers would be appreciated.
>
I did this once so that users could only push to branches in a namespace
beginning with their username, so the user "hgb" could only write to
"hgb/master" and never to "master" directly (for example). This provides
maximum freedom to the users while making sure they never muck about with
any "official" branches.
The script to accomplish this is, alas, lost.
Denying non-fast-forwards even if --force is in effect is a config option
these days, I think.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2009-08-04 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 18:16 disable branch modification Ishaaq Chandy
2009-08-04 13:36 ` Andreas Ericsson [this message]
2009-08-04 16:50 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A78396B.70004@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=ishaaq@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).