tag:help.appveyor.com,2012-11-13:/discussions/questions/3692-filtering-buildsAppVeyor: Discussion 2018-10-19T08:18:19Ztag:help.appveyor.com,2012-11-13:Comment/423933402017-04-20T20:02:56Z2017-04-20T20:02:56ZFiltering builds<div><p>Hi Max,</p>
<p>Just to confirm that we are talking about <a href="https://www.appveyor.com/docs/how-to/filtering-commits/">Setting up commits filtering</a> part in our documentation.<br>
All information used in those filters is being read by AppVeyor from WebHook payload, which came from Git provider (GitHub, BitBucket, etc.) after push or pull request happen. AppVeyor does not compare anything itself.</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/423933402017-04-20T22:57:51Z2017-04-20T22:57:51ZFiltering builds<div><p>Thank you Ilya! Yes, I meant commit filtering that you linked.</p>
<p>Your filtering rules are specified in terms of files changed. So I was expecting you obtain some diff for each push.</p>
<p>The payload <a href="https://developer.github.com/v3/activity/events/types/#pushevent">contains</a> <code>head</code> and <code>before</code> keys, but not the diff. So I thought you would take the diff between the two commits. In this case, I wanted to know how you deal with rebase or a <code>push --force</code>, which result in <code>before</code> commit becoming unreachable and so absent from the cloned repo.</p>
<p>The only diffs I found in the Webhook payloads are for PRs, not for pushes.</p></div>Max Moroz