Issue Dependencies
This event occurs when there is activity relating to issue dependencies, such as blocking or blocked-by relationships.
Actions
| Action | Sent when |
|---|---|
blocked-by-added | An issue was marked as blocked by another issue. |
blocked-by-removed | The blocked by relationship between an issue and another issue was removed. |
blocking-added | An issue was marked as blocking another issue. |
blocking-removed | The blocking relationship between an issue and another issue was removed. |
Payload
Fields of the delivery for the first action above. Every action shares the event's core fields.
| Field | Type | Required | Description |
|---|---|---|---|
action | string | Yes | |
blocked_issue_id | number | No | The ID of the blocked issue. |
blocked_issue | object | No | Issues are a great way to keep track of tasks, enhancements, and bugs for your projects. |
blocking_issue_id | number | No | The ID of the blocking issue. |
blocking_issue | object | No | Issues are a great way to keep track of tasks, enhancements, and bugs for your projects. |
blocking_issue_repo | object | No | A repository on GitHub. |
installation | object | No | The GitHub App installation. Webhook payloads contain the installation property when the event is configured |
organization | object | Yes | A GitHub organization. Webhook payloads contain the organization property when the webhook is configured for an |
repository | object | Yes | The repository on GitHub where the event occurred. Webhook payloads contain the repository property |
sender | object | Yes | A GitHub user. |
Subscribing
To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions.