[Dune-devel] Protected branches for dune-common

Dominic Kempf dominic.r.kempf at gmail.com
Mon Jul 12 10:31:29 CEST 2021


Hey Markus,
hey René,

dune-common is indeed a bit more equal as it allows "No One" to push to
releases/* branches, whereas the other Core modules allow maintainers to do
so.
I personally think this is an oversight and we could change it to
Maintainers only.

Best,
Dominic

On Mon, Jul 12, 2021 at 10:24 AM René Heß <rene.hk-edv at gmx.de> wrote:

> Hi Markus,
>
> looking at the protected branches in
>
> https://gitlab.dune-project.org/core/dune-common/-/settings/repository
>
> releases/* is indeed protected and no one is allowed to push them. You
> are owner in dune-common so you already have the highest access role so
> you could change that.
>
> The alternative would be creating a new branch and merging it into the
> releases/2.8 branch.
>
> I did not change anything as it seems to be intentional and I'm not in a
> position to change the behaviour (in the sense of 'I should not', as a
> gitlab admin I could of course). Just pointing out the current state :).
>
>
> Thanks for working on the release,
> best regards,
> René
>
>
>
>
>
> Markus Blatt <markus at dr-blatt.de> writes:
>
> > Hi,
> >
> > can somebody please give me push rights to releases/2.8 in dune-common?
> Without that it is rather
> > cumbersome to do a release. Maybe I am in the wrong group?
> >
> > Markus
> >
> > _______________________________________________
> > Dune-devel mailing list
> > Dune-devel at lists.dune-project.org
> > https://lists.dune-project.org/mailman/listinfo/dune-devel
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at lists.dune-project.org
> https://lists.dune-project.org/mailman/listinfo/dune-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20210712/de874cb6/attachment.htm>


More information about the Dune-devel mailing list