`head` should be`after` in PushEvent#966

Closed

rco-ableton wants to merge1 commit intogithub:masterfromrco-ableton:patch-1

Closed

`head` should be`after` in PushEvent#966

rco-ableton wants to merge1 commit intogithub:masterfromrco-ableton:patch-1

Conversation

Copy link

rco-ableton commentedJan 25, 2016

The actual payload JSON contains anafter entry but nohead entry, so I assume this should beafter in the description.

head should beafter in PushEvent

b0c03b7

The actual payload JSON contains an `after` entry but no `head` entry, so I assume this should be `after` in the description.

Copy link

Member

izuzak commentedJan 25, 2016

Thanks for submitting a pull request,@rco-ableton. That's actually expected behavior -- please see the note at the top of that section:

https://developer.github.com/v3/activity/events/types/#pushevent

"The Events API PushEvent payload is described in the table below. The example payload below that is from a webhook delivery and will differ from the Events API PushEvent payload."

The payloads for the push event send via webhooks does not match the payload for the PushEvent made available via the Events API, and that's expected behavior. You'll notice that API responses which include a PushEvent have ahead field in the JSON body.