Sub Issues
This event occurs when there is activity relating to sub-issues.
Actions
| Action | Sent when |
|---|---|
parent-issue-added | A parent issue was added to an issue. |
parent-issue-removed | A parent issue was removed from an issue. |
sub-issue-added | A sub-issue was added to an issue. |
sub-issue-removed | A sub-issue was removed from an issue. |
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 | |
parent_issue_id | number | No | The ID of the parent issue. |
parent_issue | object | No | Issues are a great way to keep track of tasks, enhancements, and bugs for your projects. |
parent_issue_repo | object | No | A repository on GitHub. |
sub_issue_id | number | Yes | The ID of the sub-issue. |
sub_issue | object | Yes | Issues are a great way to keep track of tasks, enhancements, and bugs for your projects. |
installation | object | No | The GitHub App installation. Webhook payloads contain the installation property when the event is configured |
organization | object | No | 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.