Remove Pull Request Reviewers

github.remove_pull_request_reviewers
ActionBusiness appsconnection required

Calls DELETE /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers.

Withdraw a review request from users or teams.

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

5 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
owner
Repository owner — the user or organisation login. Supports {{ }}.
stringYes——octocat
repo
Repository name, without the owner prefix. Supports {{ }}.
stringYes——hello-world
pull_number
Pull request number as shown in the UI (not the internal id).
stringYes——1
reviewers
GitHub usernames to request, as a JSON array or a comma-separated list.
arrayNo—array of string["octocat"]
team_reviewers
Team slugs to request, as a JSON array or a comma-separated list.
arrayNo—array of string["core-team"]
  • At least one of reviewers, team_reviewers must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "owner": "octocat",
  "pull_number": "1",
  "repo": "hello-world",
  "reviewers": [
    "octocat"
  ],
  "team_reviewers": [
    "core-team"
  ]
}

Output

One shape.

result

FieldTypeExample
ok
True when GitHub accepted the call.
booleantrue
reviewers
Usernames now requested on the pull request.
array—
team_reviewers
Team slugs now requested on the pull request.
array—
{
  "ok": true,
  "reviewers": [],
  "team_reviewers": []
}

See Remove Pull Request Reviewers 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.