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 <git...@apache.org>
> >>> *Subject: **Protected Branches for db-site.git has been updated*
> >>> *Date: *January 23, 2022 at 9:13:17 AM PST
> >>> *To: *priv...@db.apache.org
> >>> *Reply-To: *priv...@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
> >> c...@apache.org
> >>
>
