Commit87509e6

committed

Repository and sender aren't in Events API

The `repository` and `sender` fields are not present in the Events API payloads (but are present in webhook deliveries). This notes that difference (which was previously indicated to be structurally identical JSON to the literal webhook examples except where noted).

1 parent37f2bc6 commit87509e6Copy full SHA for 87509e6

File tree

1 file changed

-1

lines changed

content/v3/activity/events
- types.md

1 file changed

-1

lines changed

`‎content/v3/activity/events/types.md‎`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -9,7 +9,7 @@ determined by its event type.`
`9`	`9`
`10`	`10`	`Event names are used by[repository webhooks](/v3/repos/hooks/) to specify`
`11`	`11`	`which events the webhook should receive. The included payloads below are from webhook deliveries but`
`12`		-match events returned by the[Events API](/v3/activity/events/) (except where noted). Theevents API uses the CamelCased name (e.g.`CommitCommentEvent`) in the`type` field of an event object.
	`12`	+match events returned by the[Events API](/v3/activity/events/) (except where noted). TheEvents API uses the CamelCased name (e.g.`CommitCommentEvent`) in the`type` field of an event object and does not include the`repository` or`sender` fields in the event payload object.
`13`	`13`
`14`	`14`
`15`	`15`	`Note that some of these events may not be rendered in timelines.`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit87509e6

File tree

1 file changed

1 file changed

`‎content/v3/activity/events/types.md‎`

0 commit comments