Good Point. Would be nice if the jira issues could be generated
automatically... is anybody aware of such a service?
Send from my mobile device
> Am 17.10.2014 um 21:43 schrieb sebb :
>
> A related issue: when filing a JIRA from the pull request, please
> include more than just the PR URL.
>
>
A related issue: when filing a JIRA from the pull request, please
include more than just the PR URL.
I think it's important that the JIRA can be understood without having
to follow the URL.
We don't have control over Github; it could disappear or change URL one day.
I think it's important that o
Le 17/10/2014 10:16, Duncan Jones a écrit :
> Do you happen to know if GitHub will react to commit messages from SVN
> in order to close PRs, such as described in [1]?
Yes it does.
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-
On 17 October 2014 09:07, Emmanuel Bourg wrote:
> Le 17/10/2014 09:44, Duncan Jones a écrit :
>
>> Is there a preferred approach to take here? I have a GitHub account,
>> so presumably I could be given rights to the repositories I commit to
>> (lang) and this would allow me to merge PRs directly i
Le 17/10/2014 09:44, Duncan Jones a écrit :
> Is there a preferred approach to take here? I have a GitHub account,
> so presumably I could be given rights to the repositories I commit to
> (lang) and this would allow me to merge PRs directly into trunk. Would
> such changes be reflected in our SVN
Hi everyone,
Some of our contributors like to use GitHub pull requests (PRs) as a
means of providing patches. Until now, I've tended to access the
.patch version of these pull requests and apply them in SVN.
Is there a preferred approach to take here? I have a GitHub account,
so presumably I coul
