Acl extension to prevent pushing into default branch

[Lasse Vågsæther Karlsen]

On Fri, Jan 7, 2011 at 10:32, Felix Dorner <fdorner at tuenti.com> wrote:

> Hi,
>
> I need a setup a repository so that only users in a certain unix (LDAP
> managed) group are allowed to push changes to the default branch.
> Everyone else should have 'read' access to all branches and write
> access to all branches except the default. Is this possible with the
> ACL extension, and if so, could someone please give an example?
> Especially I don't seem to find a solution that specifies distinct
> permissions for read (pull) and write(push) operations.
>
> Thanks,
> Felix
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>

Access rights is usually done on a per-repository level.

Couldn't an alternate workflow work? You create a clone of the repository
with more open access rights, and let those people with central commit
access do the pulling and pushing between the two?

This is usually how it is done.

ie. you, as a normal developer, would push all your changes to a repository
you have push access to. Then later I would verify your changes, and push
those further on to the central repository.

I assume you want to do this because you use the default branch to run CI or
update a live server with, or similar actions, and you want to prevent bad,
untested, code to be pushed prematurely.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20110107/fdc371af/attachment.htm>