On Mon, Apr 4, 2016 at 11:14 AM, Sean Busbey <[email protected]> wrote: > You're correct, a github PR only targets a single branch and Travis-CI > only checks how the PR does at its own commit hash (that is, it > doesn't even check what the target branch would look like post-merge). >
Hey Sean, it looks like Travis-CI does merge into the specified merge branch before running. For example, my ListS3 PR [1] has commit 2f7e89e, but the Travis-CI status page [1] shows commit e0868c2. If you find that in github [2] you'll see it is the merge of 2f7e89e and 6f5fb59, where 6f5fb59 is the location of master when I submitted the PR. If the branch is squashed prior to the final merge, then Travis-CI will be run a second time against the latest master or pretty close to it, depending on how quickly a committer comes along :) Adam [1] https://github.com/apache/nifi/pull/238 [2] https://travis-ci.org/apache/nifi/builds/114423137 [3] https://github.com/apache/nifi/commit/e0868c242503cda3c4ca14140164e0e7f3f7a8fe
