[petsc-dev] Fwd: [petsc-users] new book introducing PETSc for PDEs

[Ed Bueler]

I think "The ability to restrict branches is a type of branch protection
that's available for public and private repositories owned by organizations
in GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server."
probably applies to ceed/libceed.  Or maybe they've tied this to
organizations (though they don't say that). In any case, the "Restrict who
can push to matching branches" button [see
https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/enabling-branch-restrictions]
is just not there on my settings/branches page.

Ed

On Mon, Nov 2, 2020 at 2:00 PM Jed Brown <jed at jedbrown.org> wrote:

> Ed Bueler <elbueler at alaska.edu> writes:
>
> >> You should be able to click "Add rule" here
> >> https://github.com/bueler/p4pdes/settings/branches
> >
> > Nope.  Try it.  Restricting branches is not one of the options under
> > "github pro" public repo ownership.  (Nothing about the github
> > manage access interface is informative about admins and/or
> > collaborator permissions etc.)
> >
> > However, adding required MR reviews onto master is an option, and I can
> > leave "Include Admins" unchecked; I have done that.   I'll see if these
> > settings are smooth for me.
>
> I think that's what I meant. In any case, we use it in libceed and I see
> the ability in other personal repositories. I'm not sure what's missing
> from your view, but requiring MRs for non-admin (you) should be enough.
>


-- 
Ed Bueler
Dept of Mathematics and Statistics
University of Alaska Fairbanks
Fairbanks, AK 99775-6660
306C Chapman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20201102/56a8b801/attachment.html>