You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@celix.apache.org by Roy Lenferink <le...@gmail.com> on 2019/09/21 09:19:42 UTC
Protected 'develop' branch for Celix
Hi all,
I'd like to propose the idea of having the 'develop' branch for Celix
protected.
This means branch-deletion and force-pushes are not allowed anymore.
Because Celix development happens on the develop branch we definitely don't
want that branch to get deleted (be it by accident). Because the Gitbox and
GitHub repositories are synced it is only a single click to delete a
non-protected
branch (our 'master' branch already has this enabled).
I'd like to do the same for the celix-site repository and enable branch
protection
on the 'master' and 'asf-site' branches ('master' branch containing source
code for
celix.a.o, 'asf-site' containing generated code by Jenkins which is being
used to host celix.a.o).
If there are no objections within the next 72 hours I'll create a ticket
with
INFRA to enable this.
Best,
Roy
Re: Protected 'develop' branch for Celix
Posted by Roy Lenferink <le...@gmail.com>.
Issue created: https://issues.apache.org/jira/browse/INFRA-19150
Op zo 22 sep. 2019 om 21:05 schreef Pepijn Noltes <pe...@gmail.com>:
> Hi Roy,
>
> On Sat, Sep 21, 2019 at 11:20 AM Roy Lenferink <le...@gmail.com>
> wrote:
> >
> > Hi all,
> >
> > I'd like to propose the idea of having the 'develop' branch for Celix
> > protected.
> > This means branch-deletion and force-pushes are not allowed anymore.
> > Because Celix development happens on the develop branch we definitely
> don't
> > want that branch to get deleted (be it by accident). Because the Gitbox
> and
> > GitHub repositories are synced it is only a single click to delete a
> > non-protected
> > branch (our 'master' branch already has this enabled).
> >
> > I'd like to do the same for the celix-site repository and enable branch
> > protection
> > on the 'master' and 'asf-site' branches ('master' branch containing
> source
> > code for
> > celix.a.o, 'asf-site' containing generated code by Jenkins which is being
> > used to host celix.a.o).
> >
> > If there are no objections within the next 72 hours I'll create a ticket
> > with
> > INFRA to enable this.
> >
> > Best,
> > Roy
>
> Sound very reasonable, good initiative !
>
> Greetings,
> Pepijn
>
Re: Protected 'develop' branch for Celix
Posted by Pepijn Noltes <pe...@gmail.com>.
Hi Roy,
On Sat, Sep 21, 2019 at 11:20 AM Roy Lenferink <le...@gmail.com> wrote:
>
> Hi all,
>
> I'd like to propose the idea of having the 'develop' branch for Celix
> protected.
> This means branch-deletion and force-pushes are not allowed anymore.
> Because Celix development happens on the develop branch we definitely don't
> want that branch to get deleted (be it by accident). Because the Gitbox and
> GitHub repositories are synced it is only a single click to delete a
> non-protected
> branch (our 'master' branch already has this enabled).
>
> I'd like to do the same for the celix-site repository and enable branch
> protection
> on the 'master' and 'asf-site' branches ('master' branch containing source
> code for
> celix.a.o, 'asf-site' containing generated code by Jenkins which is being
> used to host celix.a.o).
>
> If there are no objections within the next 72 hours I'll create a ticket
> with
> INFRA to enable this.
>
> Best,
> Roy
Sound very reasonable, good initiative !
Greetings,
Pepijn