[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Work Branches
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2019-10-06 18:19:25
Message-ID: CA+XidOFP6omiQLUbitBeagjVSNUQg_EpaFJi1R4YdM6+qzCM-g () mail ! gmail ! com
[Download RAW message or body]

On Mon, Oct 7, 2019 at 4:28 AM Luigi Toscano <luigi.toscano@tiscali.it> wrote:
>
> Ben Cooksley ha scritto:
> > Hi all,
> >
> > Recently we had a discussion (which I think may have ended up spread
> > over a couple of mailing lists in the end) concerning branches and the
> > ability to force push to them.
> >
> > [...]
> > 2) Protect all branches, aside from a given prefix (proposed to be work/)
> >
> > I'd like to clean this up and sort out the policy we want to have
> > surrounding this so we can move forward.
> >
>
> As many others pointed out, 2) seems to be really the cleanest solution.
>
> Just to be clear: will this apply to all repositories including personal
> clones/scratches (which are now the same thing, I guess), or just to the
> "official" repositories?

Just to official repositories.

You've always been able to force push to all branches in repositories
within your personal namespace.
Please note that clones and scratch repositories will become the same
thing when we move to Gitlab.

>
> Ciao
> --
> Luigi

Cheers,
Ben
[prev in list] [next in list] [prev in thread] [next in thread]