[
https://issues.apache.org/jira/browse/IGNITE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697502#comment-14697502
]
Artem Shutak edited comment on IGNITE-1217 at 8/14/15 6:27 PM:
---------------------------------------------------------------
I'm looking for a way how to not have a requirement that pull-request should
has only commit.
I've tried "git merge --squash" from contributor branch to local master of a
commiter , but there is a big chance that local master will not be up-to-date.
So, in this case commit after squash will contain not only contributor changes.
It's a bad idea.
was (Author: ashutak):
I'm looking for a way how to not have a requirement that pull-request should
has only commit.
I've tried "git merge --squash" from contributor branch to local master of a
commiter , but there is a big chance that local master will not be up-to-date.
So, in this case commit after squash will contain not only contributor changes.
> 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)
