Acl extension to prevent pushing into default branch

[Janusz Gryczman]

Do you have "allow_push" in your hgrc file?
I have the same use case, but it looks like if that "allow_push" is taking 
presedence over acl hook and I need to have users listed always in 
"allow_push"
If I don't, then  authentication fails.
Any idea?

On Friday, January 7, 2011 4:34:36 AM UTC-6, Felix Dorner wrote:
>
> 2011/1/7 Lasse Vågsæther Karlsen <la... at vkarlsen.no <javascript:>>:
> > 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?
>
> Sounds good, and I'm sure we'll do something like that in the future.
>
> For now I have to stick with the acl solution. It looks like this works:
>
> [hooks]
>
> pretxncommit.acl = python:hgext.acl.hook
> pretxnchangegroup.acl = python:hgext.acl.hook
>
> [acl]
> sources = serve
>
> [acl.allow.branches]
> default = @ubergeeks
> _______________________________________________
> Mercurial mailing list
> Merc... at selenic.com <javascript:>
> http://selenic.com/mailman/listinfo/mercurial
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140410/0290188c/attachment-0002.html>