There's no magic to it. We're doing the same, except Josh automated it in
the PR dashboard he created.

https://spark-prs.appspot.com/

Nick

On Wed, May 13, 2015 at 6:20 PM Markus Weimer <mar...@weimo.de> wrote:

> Hi,
>
> how did you set this up? Over in the REEF incubation project, we
> painstakingly create the forwards- and backwards links despite having
> the IDs in the PR descriptions...
>
> Thanks!
>
> Markus
>
>
> On 2015-05-13 11:56, Ted Yu wrote:
> > Subproject tag should follow SPARK JIRA number.
> > e.g.
> >
> > [SPARK-5277][SQL] ...
> >
> > Cheers
> >
> > On Wed, May 13, 2015 at 11:50 AM, Stephen Boesch <java...@gmail.com>
> wrote:
> >
> >> following up from Nicholas, it is
> >>
> >> [SPARK-12345] Your PR description
> >>
> >> where 12345 is the jira number.
> >>
> >>
> >> One thing I tend to forget is when/where to include the subproject tag
> e.g.
> >>  [MLLIB]
> >>
> >>
> >> 2015-05-13 11:11 GMT-07:00 Nicholas Chammas <nicholas.cham...@gmail.com
> >:
> >>
> >>> That happens automatically when you open a PR with the JIRA key in the
> PR
> >>> title.
> >>>
> >>> On Wed, May 13, 2015 at 2:10 PM Chandrashekhar Kotekar <
> >>> shekhar.kote...@gmail.com> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> I am new to open source contribution and trying to understand the
> >> process
> >>>> starting from pulling code to uploading patch.
> >>>>
> >>>> I have managed to pull code from GitHub. In JIRA I saw that each JIRA
> >>> issue
> >>>> is connected with pull request. I would like to know how do people
> >> attach
> >>>> pull request details to JIRA issue?
> >>>>
> >>>> Thanks,
> >>>> Chandrash3khar Kotekar
> >>>> Mobile - +91 8600011455
> >>>>
> >>>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
> For additional commands, e-mail: dev-h...@spark.apache.org
>
>

Reply via email to