[
https://issues.apache.org/jira/browse/IGNITE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715299#comment-14715299
]
ASF GitHub Bot commented on IGNITE-1217:
----------------------------------------
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/41
IGNITE-1217: add suffix to commit comment " - Fixes #<id>."
ignite-1217: add suffix to commit comment " - Fixes #<id>."
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashutakGG/incubator-ignite
ignite-1217-fix-comment
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/41.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #41
----
commit 485878be39b4f14794f00538d8063b552f14fbda
Author: ashutak <ashu...@gridgain.com>
Date: 2015-08-26T18:27:28Z
ignite-1217: add suffic to comment " - Fixes #<id>."
----
> TC triggering by github pull-requests
> -------------------------------------
>
> Key: IGNITE-1217
> URL: https://issues.apache.org/jira/browse/IGNITE-1217
> Project: Ignite
> Issue Type: Task
> Reporter: Artem Shutak
> Assignee: Artem Shutak
> Attachments: master_19fb305_ignite-1217.patch,
> master_19fb305_ignite-1217.patch_
>
>
> Need to investigate possibility of auto triggering TC by pull requests.
> Expected approach
> - contributor creates fork of apache git repo mirror at github
> - working with own fork, creates branches, commits, pushes
> - create a pull request with changes from own fork to apache ignite mirror on
> github
> - TC automatically trigger builds for the pull-request
> - if TC green then a commiter apply changes to apache git repo (not to mirror
> on github)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
