Delete Issue Comment
github.delete_issue_comment
ActionBusiness appsconnection required
Calls DELETE /repos/{owner}/{repo}/issues/comments/{comment_id}.
Delete an issue or pull request comment.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- GitHub
- Secret shape
- the GitHub personal access token
- Resolved by
- config.connection_id, else node.connection_id, else the tenant's sole GitHub connection
Configuration
3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
owner Repository owner — the user or organisation login. Supports {{ }}. | string | Yes | — | — | octocat |
repo Repository name, without the owner prefix. Supports {{ }}. | string | Yes | — | — | hello-world |
comment_id Numeric id of the comment, as returned by list_issue_comments. | string | Yes | — | — | 1 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"comment_id": "1",
"owner": "octocat",
"repo": "hello-world"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when GitHub accepted the call. | boolean | true |
comment_id The comment's id. | string | — |
html_url Link to the comment. | string | — |
{
"comment_id": "",
"html_url": "",
"ok": true
}Solutions with GitHub
See Delete Issue Comment run in a workflow.
In a technical demo we add the GitHub connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.