Hello,
On Monday, 12 August 2019 13:48:46 CEST David Faure wrote:
> In any case, we should be able to make a list of stable branches,
> especially if we can use wildcards like Applications/*.
And that's kind of the way GitLab works IIUC. By default only master is
protected, but you can set extra
El dilluns, 12 d’agost de 2019, a les 11:38:50 CEST, Ben Cooksley va escriure:
> Those familiar to Git will be aware that it is very much possible to
> limit the scope of hooks like our Notification hooks, while still
> allowing them to be caught when entering branches that are subject to
> Notific
On lundi 12 août 2019 13:04:29 CEST Ben Cooksley wrote:
> On Mon, Aug 12, 2019 at 10:54 PM Albert Vaca Cintora
>
> wrote:
> > On Mon, Aug 12, 2019, 18:46 Ben Cooksley wrote:
> >> On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca Cintora
> >>
> >> wrote:
> >> > Could we use sysadmin/repo-metadata to
On Mon, Aug 12, 2019 at 10:54 PM Albert Vaca Cintora
wrote:
>
>
> On Mon, Aug 12, 2019, 18:46 Ben Cooksley wrote:
>>
>> On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca Cintora
>> wrote:
>> >
>> > Could we use sysadmin/repo-metadata to know which branch is stable and
>> > therefore should be protec
On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca Cintora
wrote:
>
> Could we use sysadmin/repo-metadata to know which branch is stable and
> therefore should be protected and trigger the hooks for closing bugs, etc?
Unfortunately that only tells us what the current stable branch is -
it doesn't let
On Mon, Aug 12, 2019 at 6:24 PM Kevin Ottens wrote:
>
> Hello,
Hi Kevin,
>
> On Sunday, 11 August 2019 22:14:19 CEST Albert Astals Cid wrote:
> > With phabricator you can do a "force push" to your review[1], with gitlab
> > you can not[2].
> > [...]
> > [2] without having your own fork of a repo
