List Pull Request Reviews

github.list_pull_request_reviews
ActionBusiness appsconnection required

Calls GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews.

List the reviews left on a pull request.

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

4 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
max_items
Stop after this many rows; further pages are followed via the Link header.
numberNo1001–1000—

Example configuration

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

{
  "max_items": 100,
  "owner": "octocat",
  "pull_number": "1",
  "repo": "hello-world"
}

Output

One shape.

result

FieldTypeExample
reviews
The reviews this step read.
array—
reviews[].id
Review id.
number—
reviews[].state
APPROVED, CHANGES_REQUESTED, COMMENTED or PENDING.
string—
reviews[].body
The review's summary comment.
string—
reviews[].user_login
Who left the review.
string—
reviews[].html_url
Link to the review.
string—
reviews[].submitted_at
When it was submitted, ISO 8601.
string—
count
How many rows this step returned.
number—
{
  "count": 0,
  "reviews": [
    {
      "body": "",
      "html_url": "",
      "id": 0,
      "state": "",
      "submitted_at": "",
      "user_login": ""
    }
  ]
}

See List Pull Request Reviews 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.