GitHub Community
Webhook sends two requests for check_suite.requested on commit #24364
-
|
Upon commit, my GitHub App gets two requests for check_suite.requested (same check_suite.id). I’m at a loss to understand why there are two separate requests for the same ID. Because the App gets two of these, the App creates two check runs with different IDs but only one check run is desired. Does anybody know why there are two requests sent for check_suite.requested? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
xpert98:
👋 @xpert98 –– welcome to GitHub’s Support Community! Thanks for posting your question about these webhooks in relation to check suite activity. I’m interested in seeing what you’re seeing. 👀 Given a new GitHub App, could you please share the configuration and the exact steps taken to reliably reproduce those two |
Beta Was this translation helpful? Give feedback.
-
|
The repo I’m using to test out this app (“proton probot app”) is https://github.com/xpert98/proton. I’ve installed my app and have it set to have the following Repository permissions:
It has no Org or User permissions. Lastly, it is only subscribed to Check suite events. |
Beta Was this translation helpful? Give feedback.
-
|
After a lot of troubleshooting, this appears to only happen when proxying through smee! I deployed my app to AWS and it consistently receives only one check_suite request. |
Beta Was this translation helpful? Give feedback.
-
|
xpert98:
@xpert98 - Thanks for sharing that detail here! It’s great to know that you’ve isolated it down to
probot/smee-client🔴 Receives payloads then sends them to your local server - probot/smee-client |
Beta Was this translation helpful? Give feedback.
After a lot of troubleshooting, this appears to only happen when proxying through smee! I deployed my app to AWS and it consistently receives only one check_suite request.