Hi Jed,
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?
I set this restriction on
Karl Rupp r...@mcs.anl.gov writes:
Thanks! That should avoid accidental pushes to branches if git is not
configured to use the 'simple' push.default.
Yeah, I was worried about sometimes asking people to force-push branches
when they also have the ability to force-push integration branches.
Jed Brown jedbr...@mcs.anl.gov writes:
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?
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
