This sounds like a great idea from the perspective of someone like me, who would only be pushing to maint/master/next in error at this point. It would also allow slightly easier access to features which are new/experimental enough to not be in next yet. On Sep 19, 2013, at 4:35 PM, Jed Brown wrote:
> Bitbucket added support to restrict push access based on branch names > (glob matching). For example, that would allow us to have a smaller > group of people with access to merge to 'maint' or 'master'. > > Is this a feature we should start using in petsc.git? > > One tangible difference from the current model is that it would let give > more people push access to named branches which then allows an > integrator to patch up a branch for an open pull request. (When a PR > comes from a fork instead of an in-repo branch, we can't push to their > repository so we can't update the PR. This sometimes leads to tedious > fine-tuning of trivial details in the PR comments.) > > > Admins can see the branch list here: > > https://bitbucket.org/petsc/petsc/admin/branches