tag:help.appveyor.com,2012-11-13:/discussions/questions/34857-problems-with-building-pull-request-mergeAppVeyor: Discussion 2019-02-28T00:02:39Ztag:help.appveyor.com,2012-11-13:Comment/470031292019-02-25T23:40:35Z2019-02-25T23:40:35ZProblems with building pull request merge<div><p>There can be other differences with pull request builds (unavailability of secure variables to name one) that could cause a previously successful build to fail.<br>
What makes you certain that the merge is omitting certain files? You can use `type to check the contents of files you suspect to be different.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/470031292019-02-26T08:19:55Z2019-02-26T08:19:56ZProblems with building pull request merge<div><p>It's not that the merging is omitting certain files, it's that it doesn't appear to be happening at all. When inspecting over RDP even though the build log shows that it has supposedly run a <code>git fetch -q origin +refs/pull/41/merge:</code> and <code>git checkout -qf FETCH_HEAD</code> running a <code>git log</code> and looking at the files in the project folder, they are still only reflecting the state on the latest master commit and not the result of merging the pull request to master.<br>
As I say if I run those commands as in my first comment manually on the build server to a fresh directory (with the addition of the cd command which isn't shown on the build log) then all works fine.</p>
<p>What exactly do you mean when you say I can "use `type to check the contents of files you suspect to be different."?</p></div>Adriantag:help.appveyor.com,2012-11-13:Comment/470031292019-02-26T21:27:04Z2019-02-26T21:27:04ZProblems with building pull request merge<div><p>Adrian,</p>
<p>Owen meant to run command <code>- type <path-to-file></code> at some stage after <code>clone</code>, say <code>install</code> stage. This will print content of the file to the screen so we can compare some specific file content with what it supposed to be. I would recommend to run this command very first at <code>install</code> stage, for cleaner experiment.</p>
<p>Also I have to say that we have no other complains like this, though thousands of GitHub PRs build on AppVeyor every day. This should be something special. So let us please display some file content to understand the problem better.</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/470031292019-02-27T23:50:45Z2019-02-27T23:50:46ZProblems with building pull request merge<div><p>Hello,</p>
<p>Thanks to you all for your suggestions, I managed to diagnose this issue and track it down to <code>gitversion</code> pulling and overwriting the merge. Using <code>type packages.config</code> before and after this command I could see that the files had changed.<br>
I believe I have solved this problem now and the issue can be closed.</p>
<p>Thank you all for your time,</p>
<p>Adrian.</p></div>Adriantag:help.appveyor.com,2012-11-13:Comment/470031292019-02-28T00:02:38Z2019-02-28T00:02:38ZProblems with building pull request merge<div><p>Great, thanks for the update!</p></div>Ilya Finkelshteyn