Hi Felix,

I tried subscribing, forgot to mentioned that it didn't work.

Yes I prefer all commits notifications to commits@ to be setup by INFRA

I think after we move all the repos under the Apache github org the repos
will be under the management of INFRA and opening the request at that time
will make more sense.

--Carlos


On Mon, Jan 30, 2017 at 5:25 AM Felix Meschberger <[email protected]>
wrote:

> Hi,
>
> That is strange. I would have expected the email to land int the
> moderator’s queue for letting it through.
>
> One option would be to subscribe the sender to the commits@ list.
>
> The other option, as I wrote earlier is to work with Infra to set this up
>
> Regards
> Felix
>
> > Am 27.01.2017 um 02:50 schrieb Carlos Santana <[email protected]>:
> >
> > Yes Matt I bet that was one of the problem the email bouncing back as not
> > authorized.
> >
> > On Thu, Jan 26, 2017 at 1:59 PM Matt Rutkowski <[email protected]>
> wrote:
> >
> >> Thanks Carlos!
> >>
> >> and sorry that the GitHub email notification service did not work
> (perhaps
> >> for the same reason?).
> >>
> >> Kind regards,
> >> Matt
> >>
> >>
> >>
> >> From:   Carlos Santana <[email protected]>
> >> To:     "[email protected]" <[email protected]>
> >> Date:   01/26/2017 01:02 AM
> >> Subject:        sending notifications to commits mailing list
> >>
> >>
> >>
> >> I was asked by Matt to setup the integration between all our github
> repos
> >> and the commits list.
> >>
> >> I setup a single webhook trigger in our openwhisk org
> >>
> >> Then setup a OpenWhisk action to handle the push event to send the email
> >> to
> >> the list.
> >>
> >> I hit a roadblock, since I'm using a bot email
> [email protected]
> >> and
> >> this email is not authorized to post to the commits mailing list
> >>
> >> I opened an Infra ticket to see how they can help us out to move
> forward.
> >>
> >> https://issues.apache.org/jira/browse/INFRA-13403
> >>
> >> PS: Here is the repo with the sample code
> >> https://github.com/csantanapr/openwhisk-git-to-email
> >>
> >>
> >> -- Carlos
> >>
> >>
> >>
> >>
> >>
>
>

Reply via email to