You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Shazron <sh...@gmail.com> on 2014/02/25 06:17:57 UTC
Improved integration between Apache and GitHub
https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
Do we want everything on that list? I can file the issue...
Re: Improved integration between Apache and GitHub
Posted by Carlos Santana <cs...@gmail.com>.
Here is the documentation on the other verbs that should work. I'm assuming
it applies to both issues and pulls
[1] "Closing issues via commit message"
it works across repos, and can close multiples with one commit message
1: https://help.github.com/articles/closing-issues-via-commit-messages
--Carlos
On Mon, Mar 3, 2014 at 3:19 AM, Shazron <sh...@gmail.com> wrote:
> https://issues.apache.org/jira/browse/INFRA-7377
>
>
> On Mon, Mar 3, 2014 at 12:19 AM, Shazron <sh...@gmail.com> wrote:
>
> > More clarification needed from :
> >
> > > I assume this is for all the cordova repos?
> >
> > I would assume yes.
> >
> > >Do you just want a notification that something happens on github on IRC,
> > or do you want the actual comments relayed as well?
> >
> > I would think just if something happens.
> >
> > > Furthermore, please subscribe asfbot@urd.zones.apache.org to your
> dev@mailing list ( moderators can send an email to dev-subscribe-asfbot=
> > urd.zones.apache.org@cordova.apache.org and then ack the return mail)
> >
> > Who are the mods on our list? Not sure.
> >
> >
> > On Tue, Feb 25, 2014 at 1:31 PM, Shazron <sh...@gmail.com> wrote:
> >
> >> Full repo name not required, but implied. Just for completeness if
> >> someone is looking at the commit from Git ASF, not Github
> >>
> >>
> >> On Tuesday, February 25, 2014, Ian Clelland <ic...@google.com>
> wrote:
> >>
> >>> On Tue, Feb 25, 2014 at 12:54 PM, Shazron <sh...@gmail.com> wrote:
> >>>
> >>> > Something I noticed from a commit from Ian:
> >>> > https://github.com/apache/cordova-plugin-file-transfer/pull/20
> >>> >
> >>> > The github user "asfgit" automatically closed the PR from that commit
> >>> -- I
> >>> > believe github scans the commit message to associate it with an
> >>> issue/PR
> >>> > but not sure how it knows it was a merge. The relevant words in the
> >>> message
> >>> > are "closes #20".
> >>> >
> >>>
> >>> I was hoping that would happen when I wrote that commit line; I'll
> admit
> >>> that I didn't have very high hopes for it, though.
> >>>
> >>>
> >>> >
> >>> > Github has a way to refer to repos and issues, so this PR issue would
> >>> be
> >>> > "apache/cordova-plugin-file-transfer#20" so if we added to the commit
> >>> > message "Closes apache/cordova-plugin-file-transfer#20" it should
> >>> close the
> >>> > corresponding PR/issue (I hope).
> >>> >
> >>>
> >>> Is the full repo name required? I thought that the example above shows
> >>> that
> >>> it isn't, and we just need to ensure that we use one of the magic verbs
> >>> and
> >>> mention the PR by number?
> >>>
> >>>
> >>> >
> >>> >
> >>> > On Tue, Feb 25, 2014 at 6:33 AM, Michal Mocny <mm...@chromium.org>
> >>> wrote:
> >>> >
> >>> > > This is a sweet improvement, but if I read correct, doesn't address
> >>> our
> >>> > > biggest headaches:
> >>> > >
> >>> > > 1. You still cannot merge in PR from github
> >>> > > 2. We still cannot close PR ourselves
> >>> > > 3. Commits already automatically comment on corresponding JIRA
> >>> issues, so
> >>> > > this change merely bumps the timing of automatic JIRA references to
> >>> > > comments up a bit (helps discoverability, but doesn't in the end
> help
> >>> > > manage JIRA issues all that much).
> >>> > >
> >>> > > Perhaps the most interesting change is the better discoverability
> of
> >>> PR
> >>> > > from then dev ML without requiring explicit emails from the
> >>> contributor,
> >>> > > and our ability to reply directly from ML.
> >>> > >
> >>> > > -Michal
> >>> > >
> >>> > >
> >>> > > On Tue, Feb 25, 2014 at 7:24 AM, Ian Clelland <
> >>> iclelland@chromium.org
> >>> > > >wrote:
> >>> > >
> >>> > > > Yes, and can we have a pony, too?
> >>> > > >
> >>> > > > Seriously, everything on that list is a huge improvement over the
> >>> > > > mostly-one-way-replication that we're working with now.
> >>> > > >
> >>> > > > Thanks for filing that.
> >>> > > >
> >>> > > >
> >>> > > > On Tue, Feb 25, 2014 at 12:17 AM, Shazron <sh...@gmail.com>
> >>> wrote:
> >>> > > >
> >>> > > > >
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
> >>> > > > >
> >>> > > > > Do we want everything on that list? I can file the issue...
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> >>
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: Improved integration between Apache and GitHub
Posted by Shazron <sh...@gmail.com>.
https://issues.apache.org/jira/browse/INFRA-7377
On Mon, Mar 3, 2014 at 12:19 AM, Shazron <sh...@gmail.com> wrote:
> More clarification needed from :
>
> > I assume this is for all the cordova repos?
>
> I would assume yes.
>
> >Do you just want a notification that something happens on github on IRC,
> or do you want the actual comments relayed as well?
>
> I would think just if something happens.
>
> > Furthermore, please subscribe asfbot@urd.zones.apache.org to your dev@mailing list ( moderators can send an email to dev-subscribe-asfbot=
> urd.zones.apache.org@cordova.apache.org and then ack the return mail)
>
> Who are the mods on our list? Not sure.
>
>
> On Tue, Feb 25, 2014 at 1:31 PM, Shazron <sh...@gmail.com> wrote:
>
>> Full repo name not required, but implied. Just for completeness if
>> someone is looking at the commit from Git ASF, not Github
>>
>>
>> On Tuesday, February 25, 2014, Ian Clelland <ic...@google.com> wrote:
>>
>>> On Tue, Feb 25, 2014 at 12:54 PM, Shazron <sh...@gmail.com> wrote:
>>>
>>> > Something I noticed from a commit from Ian:
>>> > https://github.com/apache/cordova-plugin-file-transfer/pull/20
>>> >
>>> > The github user "asfgit" automatically closed the PR from that commit
>>> -- I
>>> > believe github scans the commit message to associate it with an
>>> issue/PR
>>> > but not sure how it knows it was a merge. The relevant words in the
>>> message
>>> > are "closes #20".
>>> >
>>>
>>> I was hoping that would happen when I wrote that commit line; I'll admit
>>> that I didn't have very high hopes for it, though.
>>>
>>>
>>> >
>>> > Github has a way to refer to repos and issues, so this PR issue would
>>> be
>>> > "apache/cordova-plugin-file-transfer#20" so if we added to the commit
>>> > message "Closes apache/cordova-plugin-file-transfer#20" it should
>>> close the
>>> > corresponding PR/issue (I hope).
>>> >
>>>
>>> Is the full repo name required? I thought that the example above shows
>>> that
>>> it isn't, and we just need to ensure that we use one of the magic verbs
>>> and
>>> mention the PR by number?
>>>
>>>
>>> >
>>> >
>>> > On Tue, Feb 25, 2014 at 6:33 AM, Michal Mocny <mm...@chromium.org>
>>> wrote:
>>> >
>>> > > This is a sweet improvement, but if I read correct, doesn't address
>>> our
>>> > > biggest headaches:
>>> > >
>>> > > 1. You still cannot merge in PR from github
>>> > > 2. We still cannot close PR ourselves
>>> > > 3. Commits already automatically comment on corresponding JIRA
>>> issues, so
>>> > > this change merely bumps the timing of automatic JIRA references to
>>> > > comments up a bit (helps discoverability, but doesn't in the end help
>>> > > manage JIRA issues all that much).
>>> > >
>>> > > Perhaps the most interesting change is the better discoverability of
>>> PR
>>> > > from then dev ML without requiring explicit emails from the
>>> contributor,
>>> > > and our ability to reply directly from ML.
>>> > >
>>> > > -Michal
>>> > >
>>> > >
>>> > > On Tue, Feb 25, 2014 at 7:24 AM, Ian Clelland <
>>> iclelland@chromium.org
>>> > > >wrote:
>>> > >
>>> > > > Yes, and can we have a pony, too?
>>> > > >
>>> > > > Seriously, everything on that list is a huge improvement over the
>>> > > > mostly-one-way-replication that we're working with now.
>>> > > >
>>> > > > Thanks for filing that.
>>> > > >
>>> > > >
>>> > > > On Tue, Feb 25, 2014 at 12:17 AM, Shazron <sh...@gmail.com>
>>> wrote:
>>> > > >
>>> > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>>> > > > >
>>> > > > > Do we want everything on that list? I can file the issue...
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
>
Re: Improved integration between Apache and GitHub
Posted by Shazron <sh...@gmail.com>.
More clarification needed from :
> I assume this is for all the cordova repos?
I would assume yes.
>Do you just want a notification that something happens on github on IRC,
or do you want the actual comments relayed as well?
I would think just if something happens.
> Furthermore, please subscribe asfbot@urd.zones.apache.org to your dev@mailing list ( moderators can send an email to dev-subscribe-asfbot=
urd.zones.apache.org@cordova.apache.org and then ack the return mail)
Who are the mods on our list? Not sure.
On Tue, Feb 25, 2014 at 1:31 PM, Shazron <sh...@gmail.com> wrote:
> Full repo name not required, but implied. Just for completeness if someone
> is looking at the commit from Git ASF, not Github
>
>
> On Tuesday, February 25, 2014, Ian Clelland <ic...@google.com> wrote:
>
>> On Tue, Feb 25, 2014 at 12:54 PM, Shazron <sh...@gmail.com> wrote:
>>
>> > Something I noticed from a commit from Ian:
>> > https://github.com/apache/cordova-plugin-file-transfer/pull/20
>> >
>> > The github user "asfgit" automatically closed the PR from that commit
>> -- I
>> > believe github scans the commit message to associate it with an issue/PR
>> > but not sure how it knows it was a merge. The relevant words in the
>> message
>> > are "closes #20".
>> >
>>
>> I was hoping that would happen when I wrote that commit line; I'll admit
>> that I didn't have very high hopes for it, though.
>>
>>
>> >
>> > Github has a way to refer to repos and issues, so this PR issue would be
>> > "apache/cordova-plugin-file-transfer#20" so if we added to the commit
>> > message "Closes apache/cordova-plugin-file-transfer#20" it should close
>> the
>> > corresponding PR/issue (I hope).
>> >
>>
>> Is the full repo name required? I thought that the example above shows
>> that
>> it isn't, and we just need to ensure that we use one of the magic verbs
>> and
>> mention the PR by number?
>>
>>
>> >
>> >
>> > On Tue, Feb 25, 2014 at 6:33 AM, Michal Mocny <mm...@chromium.org>
>> wrote:
>> >
>> > > This is a sweet improvement, but if I read correct, doesn't address
>> our
>> > > biggest headaches:
>> > >
>> > > 1. You still cannot merge in PR from github
>> > > 2. We still cannot close PR ourselves
>> > > 3. Commits already automatically comment on corresponding JIRA
>> issues, so
>> > > this change merely bumps the timing of automatic JIRA references to
>> > > comments up a bit (helps discoverability, but doesn't in the end help
>> > > manage JIRA issues all that much).
>> > >
>> > > Perhaps the most interesting change is the better discoverability of
>> PR
>> > > from then dev ML without requiring explicit emails from the
>> contributor,
>> > > and our ability to reply directly from ML.
>> > >
>> > > -Michal
>> > >
>> > >
>> > > On Tue, Feb 25, 2014 at 7:24 AM, Ian Clelland <iclelland@chromium.org
>> > > >wrote:
>> > >
>> > > > Yes, and can we have a pony, too?
>> > > >
>> > > > Seriously, everything on that list is a huge improvement over the
>> > > > mostly-one-way-replication that we're working with now.
>> > > >
>> > > > Thanks for filing that.
>> > > >
>> > > >
>> > > > On Tue, Feb 25, 2014 at 12:17 AM, Shazron <sh...@gmail.com>
>> wrote:
>> > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>> > > > >
>> > > > > Do we want everything on that list? I can file the issue...
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: Improved integration between Apache and GitHub
Posted by Shazron <sh...@gmail.com>.
Full repo name not required, but implied. Just for completeness if someone
is looking at the commit from Git ASF, not Github
On Tuesday, February 25, 2014, Ian Clelland <ic...@google.com> wrote:
> On Tue, Feb 25, 2014 at 12:54 PM, Shazron <shazron@gmail.com<javascript:;>>
> wrote:
>
> > Something I noticed from a commit from Ian:
> > https://github.com/apache/cordova-plugin-file-transfer/pull/20
> >
> > The github user "asfgit" automatically closed the PR from that commit --
> I
> > believe github scans the commit message to associate it with an issue/PR
> > but not sure how it knows it was a merge. The relevant words in the
> message
> > are "closes #20".
> >
>
> I was hoping that would happen when I wrote that commit line; I'll admit
> that I didn't have very high hopes for it, though.
>
>
> >
> > Github has a way to refer to repos and issues, so this PR issue would be
> > "apache/cordova-plugin-file-transfer#20" so if we added to the commit
> > message "Closes apache/cordova-plugin-file-transfer#20" it should close
> the
> > corresponding PR/issue (I hope).
> >
>
> Is the full repo name required? I thought that the example above shows that
> it isn't, and we just need to ensure that we use one of the magic verbs and
> mention the PR by number?
>
>
> >
> >
> > On Tue, Feb 25, 2014 at 6:33 AM, Michal Mocny <mmocny@chromium.org<javascript:;>>
> wrote:
> >
> > > This is a sweet improvement, but if I read correct, doesn't address our
> > > biggest headaches:
> > >
> > > 1. You still cannot merge in PR from github
> > > 2. We still cannot close PR ourselves
> > > 3. Commits already automatically comment on corresponding JIRA issues,
> so
> > > this change merely bumps the timing of automatic JIRA references to
> > > comments up a bit (helps discoverability, but doesn't in the end help
> > > manage JIRA issues all that much).
> > >
> > > Perhaps the most interesting change is the better discoverability of PR
> > > from then dev ML without requiring explicit emails from the
> contributor,
> > > and our ability to reply directly from ML.
> > >
> > > -Michal
> > >
> > >
> > > On Tue, Feb 25, 2014 at 7:24 AM, Ian Clelland <iclelland@chromium.org<javascript:;>
> > > >wrote:
> > >
> > > > Yes, and can we have a pony, too?
> > > >
> > > > Seriously, everything on that list is a huge improvement over the
> > > > mostly-one-way-replication that we're working with now.
> > > >
> > > > Thanks for filing that.
> > > >
> > > >
> > > > On Tue, Feb 25, 2014 at 12:17 AM, Shazron <shazron@gmail.com<javascript:;>>
> wrote:
> > > >
> > > > >
> > > > >
> > > >
> > >
> >
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
> > > > >
> > > > > Do we want everything on that list? I can file the issue...
> > > > >
> > > >
> > >
> >
>
Re: Improved integration between Apache and GitHub
Posted by Michal Mocny <mm...@chromium.org>.
Really cool. So the only part that is missing now is the ability to just
hit the "merge this PR and close". I can live with that! Great stuff.
On Tue, Feb 25, 2014 at 1:05 PM, Ian Clelland <ic...@google.com> wrote:
> On Tue, Feb 25, 2014 at 12:54 PM, Shazron <sh...@gmail.com> wrote:
>
> > Something I noticed from a commit from Ian:
> > https://github.com/apache/cordova-plugin-file-transfer/pull/20
> >
> > The github user "asfgit" automatically closed the PR from that commit --
> I
> > believe github scans the commit message to associate it with an issue/PR
> > but not sure how it knows it was a merge. The relevant words in the
> message
> > are "closes #20".
> >
>
> I was hoping that would happen when I wrote that commit line; I'll admit
> that I didn't have very high hopes for it, though.
>
>
> >
> > Github has a way to refer to repos and issues, so this PR issue would be
> > "apache/cordova-plugin-file-transfer#20" so if we added to the commit
> > message "Closes apache/cordova-plugin-file-transfer#20" it should close
> the
> > corresponding PR/issue (I hope).
> >
>
> Is the full repo name required? I thought that the example above shows that
> it isn't, and we just need to ensure that we use one of the magic verbs and
> mention the PR by number?
>
>
> >
> >
> > On Tue, Feb 25, 2014 at 6:33 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > This is a sweet improvement, but if I read correct, doesn't address our
> > > biggest headaches:
> > >
> > > 1. You still cannot merge in PR from github
> > > 2. We still cannot close PR ourselves
> > > 3. Commits already automatically comment on corresponding JIRA issues,
> so
> > > this change merely bumps the timing of automatic JIRA references to
> > > comments up a bit (helps discoverability, but doesn't in the end help
> > > manage JIRA issues all that much).
> > >
> > > Perhaps the most interesting change is the better discoverability of PR
> > > from then dev ML without requiring explicit emails from the
> contributor,
> > > and our ability to reply directly from ML.
> > >
> > > -Michal
> > >
> > >
> > > On Tue, Feb 25, 2014 at 7:24 AM, Ian Clelland <iclelland@chromium.org
> > > >wrote:
> > >
> > > > Yes, and can we have a pony, too?
> > > >
> > > > Seriously, everything on that list is a huge improvement over the
> > > > mostly-one-way-replication that we're working with now.
> > > >
> > > > Thanks for filing that.
> > > >
> > > >
> > > > On Tue, Feb 25, 2014 at 12:17 AM, Shazron <sh...@gmail.com> wrote:
> > > >
> > > > >
> > > > >
> > > >
> > >
> >
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
> > > > >
> > > > > Do we want everything on that list? I can file the issue...
> > > > >
> > > >
> > >
> >
>
Re: Improved integration between Apache and GitHub
Posted by Ian Clelland <ic...@google.com>.
On Tue, Feb 25, 2014 at 12:54 PM, Shazron <sh...@gmail.com> wrote:
> Something I noticed from a commit from Ian:
> https://github.com/apache/cordova-plugin-file-transfer/pull/20
>
> The github user "asfgit" automatically closed the PR from that commit -- I
> believe github scans the commit message to associate it with an issue/PR
> but not sure how it knows it was a merge. The relevant words in the message
> are "closes #20".
>
I was hoping that would happen when I wrote that commit line; I'll admit
that I didn't have very high hopes for it, though.
>
> Github has a way to refer to repos and issues, so this PR issue would be
> "apache/cordova-plugin-file-transfer#20" so if we added to the commit
> message "Closes apache/cordova-plugin-file-transfer#20" it should close the
> corresponding PR/issue (I hope).
>
Is the full repo name required? I thought that the example above shows that
it isn't, and we just need to ensure that we use one of the magic verbs and
mention the PR by number?
>
>
> On Tue, Feb 25, 2014 at 6:33 AM, Michal Mocny <mm...@chromium.org> wrote:
>
> > This is a sweet improvement, but if I read correct, doesn't address our
> > biggest headaches:
> >
> > 1. You still cannot merge in PR from github
> > 2. We still cannot close PR ourselves
> > 3. Commits already automatically comment on corresponding JIRA issues, so
> > this change merely bumps the timing of automatic JIRA references to
> > comments up a bit (helps discoverability, but doesn't in the end help
> > manage JIRA issues all that much).
> >
> > Perhaps the most interesting change is the better discoverability of PR
> > from then dev ML without requiring explicit emails from the contributor,
> > and our ability to reply directly from ML.
> >
> > -Michal
> >
> >
> > On Tue, Feb 25, 2014 at 7:24 AM, Ian Clelland <iclelland@chromium.org
> > >wrote:
> >
> > > Yes, and can we have a pony, too?
> > >
> > > Seriously, everything on that list is a huge improvement over the
> > > mostly-one-way-replication that we're working with now.
> > >
> > > Thanks for filing that.
> > >
> > >
> > > On Tue, Feb 25, 2014 at 12:17 AM, Shazron <sh...@gmail.com> wrote:
> > >
> > > >
> > > >
> > >
> >
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
> > > >
> > > > Do we want everything on that list? I can file the issue...
> > > >
> > >
> >
>
Re: Improved integration between Apache and GitHub
Posted by Shazron <sh...@gmail.com>.
Something I noticed from a commit from Ian:
https://github.com/apache/cordova-plugin-file-transfer/pull/20
The github user "asfgit" automatically closed the PR from that commit -- I
believe github scans the commit message to associate it with an issue/PR
but not sure how it knows it was a merge. The relevant words in the message
are "closes #20".
Github has a way to refer to repos and issues, so this PR issue would be
"apache/cordova-plugin-file-transfer#20" so if we added to the commit
message "Closes apache/cordova-plugin-file-transfer#20" it should close the
corresponding PR/issue (I hope).
On Tue, Feb 25, 2014 at 6:33 AM, Michal Mocny <mm...@chromium.org> wrote:
> This is a sweet improvement, but if I read correct, doesn't address our
> biggest headaches:
>
> 1. You still cannot merge in PR from github
> 2. We still cannot close PR ourselves
> 3. Commits already automatically comment on corresponding JIRA issues, so
> this change merely bumps the timing of automatic JIRA references to
> comments up a bit (helps discoverability, but doesn't in the end help
> manage JIRA issues all that much).
>
> Perhaps the most interesting change is the better discoverability of PR
> from then dev ML without requiring explicit emails from the contributor,
> and our ability to reply directly from ML.
>
> -Michal
>
>
> On Tue, Feb 25, 2014 at 7:24 AM, Ian Clelland <iclelland@chromium.org
> >wrote:
>
> > Yes, and can we have a pony, too?
> >
> > Seriously, everything on that list is a huge improvement over the
> > mostly-one-way-replication that we're working with now.
> >
> > Thanks for filing that.
> >
> >
> > On Tue, Feb 25, 2014 at 12:17 AM, Shazron <sh...@gmail.com> wrote:
> >
> > >
> > >
> >
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
> > >
> > > Do we want everything on that list? I can file the issue...
> > >
> >
>
Re: Improved integration between Apache and GitHub
Posted by Michal Mocny <mm...@chromium.org>.
This is a sweet improvement, but if I read correct, doesn't address our
biggest headaches:
1. You still cannot merge in PR from github
2. We still cannot close PR ourselves
3. Commits already automatically comment on corresponding JIRA issues, so
this change merely bumps the timing of automatic JIRA references to
comments up a bit (helps discoverability, but doesn't in the end help
manage JIRA issues all that much).
Perhaps the most interesting change is the better discoverability of PR
from then dev ML without requiring explicit emails from the contributor,
and our ability to reply directly from ML.
-Michal
On Tue, Feb 25, 2014 at 7:24 AM, Ian Clelland <ic...@chromium.org>wrote:
> Yes, and can we have a pony, too?
>
> Seriously, everything on that list is a huge improvement over the
> mostly-one-way-replication that we're working with now.
>
> Thanks for filing that.
>
>
> On Tue, Feb 25, 2014 at 12:17 AM, Shazron <sh...@gmail.com> wrote:
>
> >
> >
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
> >
> > Do we want everything on that list? I can file the issue...
> >
>
Re: Improved integration between Apache and GitHub
Posted by Ian Clelland <ic...@chromium.org>.
Yes, and can we have a pony, too?
Seriously, everything on that list is a huge improvement over the
mostly-one-way-replication that we're working with now.
Thanks for filing that.
On Tue, Feb 25, 2014 at 12:17 AM, Shazron <sh...@gmail.com> wrote:
>
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>
> Do we want everything on that list? I can file the issue...
>
Re: Improved integration between Apache and GitHub
Posted by Joseph Schaefer <jo...@yahoo.com>.
Temporary condition. Spark just graduated and we ran our graduation scripts but this new stuff isn't coping properly yet with the changes.
Sent from my iPhone
> On Feb 25, 2014, at 1:01 AM, Joe Bowser <bo...@gmail.com> wrote:
>
> Yes. That being said, it looks like I'm going to have to add another
> filter. I just got notifications from infrastructure-dev from
> incubator.
>
>> On Mon, Feb 24, 2014 at 9:17 PM, Shazron <sh...@gmail.com> wrote:
>> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>>
>> Do we want everything on that list? I can file the issue...
Re: Improved integration between Apache and GitHub
Posted by Joe Bowser <bo...@gmail.com>.
Yes. That being said, it looks like I'm going to have to add another
filter. I just got notifications from infrastructure-dev from
incubator.
On Mon, Feb 24, 2014 at 9:17 PM, Shazron <sh...@gmail.com> wrote:
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>
> Do we want everything on that list? I can file the issue...
Re: Improved integration between Apache and GitHub
Posted by Marcel Kinard <cm...@gmail.com>.
Nice! Looks like we'll need to tweak the ContributorWorkflow wiki when this is complete.
On Feb 25, 2014, at 3:35 AM, Shazron <sh...@gmail.com> wrote:
> Filed: https://issues.apache.org/jira/browse/INFRA-7377
Re: Improved integration between Apache and GitHub
Posted by Shazron <sh...@gmail.com>.
Filed: https://issues.apache.org/jira/browse/INFRA-7377
On Mon, Feb 24, 2014 at 9:17 PM, Shazron <sh...@gmail.com> wrote:
>
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>
> Do we want everything on that list? I can file the issue...
>
Re: Improved integration between Apache and GitHub
Posted by Josh Soref <js...@blackberry.com>.
Shazron wrote:
> Josh - there was another infra issue where I requested this,
> but infra said the location where the messages go from Github is not
>configurable:
> https://issues.apache.org/jira/browse/INFRA-7283
*sigh*, oh well, thanks for asking.
Re: Improved integration between Apache and GitHub
Posted by Shazron <sh...@gmail.com>.
Josh - there was another infra issue where I requested this, but infra said
the location where the messages go from Github is not configurable:
https://issues.apache.org/jira/browse/INFRA-7283
On Tue, Feb 25, 2014 at 8:06 AM, Josh Soref <js...@blackberry.com> wrote:
> Shazron wrote:
> >
> >
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_a
> >nd
> >
> > Do we want everything on that list? I can file the issue...
>
> Can we control which ML they send the commits to? There was a nice split
> so that dev@ was clean, and I don¹t want that undone. I don¹t mind a
> distinct ML which people can subscribe to which includes this stuff, but I
> don¹t want it personally :).
>
>
Re: Improved integration between Apache and GitHub
Posted by Josh Soref <js...@blackberry.com>.
Shazron wrote:
>
>https://blogs.apache.org/infra/entry/improved_integration_between_apache_a
>nd
>
> Do we want everything on that list? I can file the issue...
Can we control which ML they send the commits to? There was a nice split
so that dev@ was clean, and I don¹t want that undone. I don¹t mind a
distinct ML which people can subscribe to which includes this stuff, but I
don¹t want it personally :).