tag:help.appveyor.com,2012-11-13:/discussions/questions/896-test-the-merge-in-a-build-initiated-by-a-pull-requestAppVeyor: Discussion 2018-08-25T01:53:46Ztag:help.appveyor.com,2012-11-13:Comment/358550042015-01-22T21:06:08Z2015-01-22T21:06:08ZTest the merge in a build initiated by a pull request<div><p>Yeah, AppVeyor fetches virtual merge commit created by GitHub
and you should see these two additional commands in the build
log:</p>
<pre>
<code>git fetch -q origin +refs/pull/{number}/merge:
git checkout -qf FETCH_HEAD</code>
</pre></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/358550042015-01-23T11:58:52Z2015-01-23T11:58:53ZTest the merge in a build initiated by a pull request<div><p>Right, I see this command in the logs.</p>
<p>But, in a pull request that can't be automatically merged, it
built using the commit ("git checkout -qf xyz123..."). Is this the
expected thing? I thought the build would fail, as it can't merge
the source.</p></div>Diogo Mafratag:help.appveyor.com,2012-11-13:Comment/358550042015-01-23T14:45:42Z2015-01-23T14:45:42ZTest the merge in a build initiated by a pull request<div><p>No, it's not expected. Are you sure it was triggered by PR
webhook event? You may check "Recent deliveries" of project webhook
in GitHub to see what was request and AV response. Also send me AV
project name and build version to check in database.</p>
<p>Yesterday we deployed an update that should reliably prevent
starting builds for non-mergeable PRs.</p>
<p>-Feodor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/358550042015-01-23T15:10:46Z2015-01-23T15:10:48ZTest the merge in a build initiated by a pull request<div><p>Looks like this update corrected the problem. Now it is working
as expected.</p>
<p>Thank you.</p></div>Diogo Mafratag:help.appveyor.com,2012-11-13:Comment/358550042015-01-23T15:11:51Z2015-01-23T15:11:51ZTest the merge in a build initiated by a pull request<div><p>Great, thanks for the update!</p>
<p>-Feodor</p></div>Feodor Fitsner