GitHub commit not detected

altendky's Avatar


02 Nov, 2017 06:59 PM

All my commits so far today have been built up until the latest, Set icon for main window. Is there something I can do to trigger a manual check with GitHub?

It's only a first internal 'demo' release so not a big deal but ironically that's the commit I expected to get released... :]


  1. 1 Posted by altendky on 02 Nov, 2017 07:22 PM

    altendky's Avatar

    Maybe just a temporary glitch. Pushing a tag for that commit triggered it.

  2. Support Staff 2 Posted by Ilya Finkelshte... on 02 Nov, 2017 07:54 PM

    Ilya Finkelshteyn's Avatar

    Hmm, please check if webhook was sent by GitHub when you did initial commit and what was response from AppVeyor? You can find it on GitHub project, Settings / Webhooks / AppVeyor webhook / Recent deliveries.
    And if it was sent, and AppVeyor response was 204, please send us exact time with timezone it was sent and GitHub delivery ID.

  3. 3 Posted by altendky on 03 Nov, 2017 12:26 PM

    altendky's Avatar

    Thanks for pointing that out. I had the silly idea of looking in my settings rather than project settings. :[ Looking there I see a simple service timeout with the option to redeliver. Sorry for the distraction and I'll look there in the future.


  4. Support Staff 4 Posted by Ilya Finkelshte... on 03 Nov, 2017 05:10 PM

    Ilya Finkelshteyn's Avatar

    Feel free to ping when needed :) I did not see webhook arrived in our traces so asked you to check. As long as GitHub status was OK that time, this was probably short term networking issue somewhere in between.

  5. altendky closed this discussion on 09 Nov, 2017 05:18 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? 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