Fwd: Protected Branches for db-site.git has been updated

[Craig Russell <ap...@gmail.com>]

So how do we get Protected Branches messages to go to notifications@

And why do we get these messages anyway???

Craig

> Begin forwarded message:
> 
> From: GitBox <gi...@apache.org>
> Subject: Protected Branches for db-site.git has been updated
> Date: January 23, 2022 at 9:13:17 AM PST
> To: private@db.apache.org 
> Reply-To: private@db.apache.org
> 
> 
> The following changes were applied to db-site by mbo.
> 
> GitHub Protected Branches has been enabled on branch=main
> 
> With regards,
> ASF Infra.
> 

Craig L Russell
clr@apache.org

Re: Fwd: Protected Branches for db-site.git has been updated

[Tilmann <ti...@gmx.de>]

Hi Gavin,

thanks for the hint.
We appear to get those for *every* commit, and most commits do not touch
the .asf.yaml files.

However, I now assume this happens because the repository is not
"active" yet, i.e. the .asf.yaml file references a branch that does not
exist. This probably confuses the .asf.yaml processor and it emits those
messages for every commit.

I think the repository is close to being mature enough for being
"activated", let's hope the messages stop occurring then.

Thanks,
Til

On 25/01/2022 07:49, Gavin McDonald wrote:
>
> On 2022/01/24 20:45:04 Tilmann Zäschke wrote:
>> Ah, now I see what you mean, I have no  idea why we have those messages...
> Committers can change the protected branch settings in your repositories, by tweaking a .asf.yaml file. These are important changes and so PMC oversight is required and therefore hard coded to go to your private list.
>
> HTH
>
> Gav...
>
>> Til
>>
>> On 24/01/2022 21:11, Tilmann wrote:
>>> I think it is an admin update, so slightly more important than a commit.
>>> I am not sure where they go now, we would have to try. These messages
>>> were sent before I changed the email list targets.
>>>
>>> Til
>>>
>>> On 24/01/2022 06:44, Craig Russell wrote:
>>>> So how do we get Protected Branches messages to go to notifications@
>>>>
>>>> And why do we get these messages anyway???
>>>>
>>>> Craig
>>>>
>>>>> Begin forwarded message:
>>>>>
>>>>> *From: *GitBox <gi...@apache.org>
>>>>> *Subject: **Protected Branches for db-site.git has been updated*
>>>>> *Date: *January 23, 2022 at 9:13:17 AM PST
>>>>> *To: *private@db.apache.org
>>>>> *Reply-To: *private@db.apache.org
>>>>>
>>>>>
>>>>> The following changes were applied to db-site by mbo.
>>>>>
>>>>> GitHub Protected Branches has been enabled on branch=main
>>>>>
>>>>> With regards,
>>>>> ASF Infra.
>>>>>
>>>> Craig L Russell
>>>> clr@apache.org
>>>>

Re: Fwd: Protected Branches for db-site.git has been updated

[Gavin McDonald <gm...@apache.org>]

On 2022/01/24 20:45:04 Tilmann Zäschke wrote:
> Ah, now I see what you mean, I have no  idea why we have those messages...

Committers can change the protected branch settings in your repositories, by tweaking a .asf.yaml file. These are important changes and so PMC oversight is required and therefore hard coded to go to your private list.

HTH

Gav...

> 
> Til
> 
> On 24/01/2022 21:11, Tilmann wrote:
> >
> > I think it is an admin update, so slightly more important than a commit.
> > I am not sure where they go now, we would have to try. These messages
> > were sent before I changed the email list targets.
> >
> > Til
> >
> > On 24/01/2022 06:44, Craig Russell wrote:
> >> So how do we get Protected Branches messages to go to notifications@
> >>
> >> And why do we get these messages anyway???
> >>
> >> Craig
> >>
> >>> Begin forwarded message:
> >>>
> >>> *From: *GitBox <gi...@apache.org>
> >>> *Subject: **Protected Branches for db-site.git has been updated*
> >>> *Date: *January 23, 2022 at 9:13:17 AM PST
> >>> *To: *private@db.apache.org
> >>> *Reply-To: *private@db.apache.org
> >>>
> >>>
> >>> The following changes were applied to db-site by mbo.
> >>>
> >>> GitHub Protected Branches has been enabled on branch=main
> >>>
> >>> With regards,
> >>> ASF Infra.
> >>>
> >>
> >> Craig L Russell
> >> clr@apache.org
> >>
> 

Re: Fwd: Protected Branches for db-site.git has been updated

[Tilmann Zäschke <za...@gmx.de>]

Ah, now I see what you mean, I have no  idea why we have those messages...

Til

On 24/01/2022 21:11, Tilmann wrote:
>
> I think it is an admin update, so slightly more important than a commit.
> I am not sure where they go now, we would have to try. These messages
> were sent before I changed the email list targets.
>
> Til
>
> On 24/01/2022 06:44, Craig Russell wrote:
>> So how do we get Protected Branches messages to go to notifications@
>>
>> And why do we get these messages anyway???
>>
>> Craig
>>
>>> Begin forwarded message:
>>>
>>> *From: *GitBox <gi...@apache.org>
>>> *Subject: **Protected Branches for db-site.git has been updated*
>>> *Date: *January 23, 2022 at 9:13:17 AM PST
>>> *To: *private@db.apache.org
>>> *Reply-To: *private@db.apache.org
>>>
>>>
>>> The following changes were applied to db-site by mbo.
>>>
>>> GitHub Protected Branches has been enabled on branch=main
>>>
>>> With regards,
>>> ASF Infra.
>>>
>>
>> Craig L Russell
>> clr@apache.org
>>

Re: Fwd: Protected Branches for db-site.git has been updated

[Tilmann <ti...@gmx.de>]

I think it is an admin update, so slightly more important than a commit.
I am not sure where they go now, we would have to try. These messages
were sent before I changed the email list targets.

Til

On 24/01/2022 06:44, Craig Russell wrote:
> So how do we get Protected Branches messages to go to notifications@
>
> And why do we get these messages anyway???
>
> Craig
>
>> Begin forwarded message:
>>
>> *From: *GitBox <gi...@apache.org>
>> *Subject: **Protected Branches for db-site.git has been updated*
>> *Date: *January 23, 2022 at 9:13:17 AM PST
>> *To: *private@db.apache.org
>> *Reply-To: *private@db.apache.org
>>
>>
>> The following changes were applied to db-site by mbo.
>>
>> GitHub Protected Branches has been enabled on branch=main
>>
>> With regards,
>> ASF Infra.
>>
>
> Craig L Russell
> clr@apache.org
>