Re: Restricting access to a branch

Stephen Hemminger [off-list ref] writes:

Is there some standard way to freeze a branch and not allow anymore changes to
be pushed?

Yes, I know it is possible by playing with hook files, but that doesn't seem
very admin friendly.

If you do not want to use hooks, then the answer is no.  Sorry.

On Wed, 21 May 2008, Junio C Hamano wrote:

Stephen Hemminger [off-list ref] writes:

quoted

Is there some standard way to freeze a branch and not allow anymore changes to
be pushed?

Yes, I know it is possible by playing with hook files, but that doesn't seem
very admin friendly.

If you do not want to use hooks, then the answer is no.  Sorry.

Hmm. I don't think that's strictly true.

What you *can* do is:

 - rename the branch to something that includes a slash (aka 
   subdirectory). Let's call it "frozen/mybranch" as an example.

 - do a 'git gc' to make sure that branch is in the packed refs file.

 - make the subdirectory of that branch is unwritable (ie just do 
   something like "chmod -w refs/heads/frozen")

and now the filesystem permissions should mean that you can't actually 
update that branch any more, even though you can read it.

Of course, if the person has full shell access, then they can still just 
undo those file permissions, but at least it should be protected from 
accidentally being overwritten.

This is all totally untested, of course.

		Linus