[petsc-dev] Push restrictions on branches

[Jed Brown]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130919/d8f19bc0/attachment.sig>