Skip to content

repo sync #5585

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 21, 2021
Merged

repo sync #5585

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8054606
Webhook restructuring follow-up (#18872)
rachmari Apr 21, 2021
3a22481
Merge branch 'main' into repo-sync
Octomerger Apr 21, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 3 additions & 7 deletions content/developers/webhooks-and-events/webhook-events-and-payloads.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,9 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.

Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment.

Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event.
#### Availability

- {% data variables.product.prodname_github_app %}s with the `content_references:write` permission

#### Webhook payload example

Expand Down Expand Up @@ -1008,12 +1010,6 @@ Deliveries for `review_requested` and `review_request_removed` events will have

{% endnote %}

{% tip %}

**Note**: The webhook payload example following the table differs significantly from the Events API payload described in the table. Among other differences, the webhook payload includes both `sender` and `pusher` objects. Sender and pusher are the same user who initiated the `push` event, but the `sender` object contains more detail.

{% endtip %}

#### Availability

- Repository webhooks
Expand Down