Re-run AppVeyor on subsequent commits to a pull request
First off - I'm new to AppVeyor and Github so I may just not understand.... but:
When someone creates a PR, AppVeyor runs and lets us know if the project built and unit tests pass. Cool.
If the build or unit tests fail, I add a comment and don't merge the PR.
The dev fixes their issue and commits to the same PR.
At this point, is there a way for me to run AppVeyor again to see if the problem is fixed? Our current workflow only re-runs AppVeyor after I merge the PR (still unsure of whether the unit test or build were fixed).
Am I missing a step?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac

Support Staff 1 Posted by Feodor Fitsner on 21 Oct, 2015 05:01 PM
Hi Mike,
When PR is updated there is "PR sync" event fires to AppVeyor webhook and it should start a new build.
2 Posted by Mike on 22 Oct, 2015 06:28 PM
Thanks Feodor. AppVeyor is not running again when a dev pushes to their remote branch that initiated the PR.
I attached my webhooks setting for AppVeyor in Github just to make sure we're on the same page.
Should the sync event fire automatically when a dev pushes to their remote repo, or is there another step to initiate the sync?
Thanks again.
3 Posted by Mike on 22 Oct, 2015 07:13 PM
I think I fixed this issue. I set "develop" to be my default branch in github. This is the branch I was trying to merge into on the previous PRs. This scenario is working now.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:01 AM.