In this guide

Review a Pull Request

Approve, request changes, or leave a review comment.

Action referenceCreate

What this action does #

First, connect GitHub in Services. Then open Actions → + → GitHub and choose Review a Pull Request.

What a run does

Running or testing this action creates something in your connected service.

More about this action

Event decides what the review is. APPROVE with no body is the one-tap approval; REQUEST_CHANGES and COMMENT both require a body, and 422 is what an empty one gets.

Leave Event unset to open a pending review that nobody sees until it is submitted from the website. That is rarely what a shortcut wants.

GitHub refuses to let anyone approve their own pull request — that is also a 422, and no permission fixes it.

Inputs to fill in #

Open an input to choose its value. Keep a fixed value with Text, receive it from Shortcuts, ask when the action runs, or use an Earlier Step. Read how input sources work.

Owner

RequiredText

User or organisation.

This input offers a picker for repository from your connected account. You can also supply its value directly.

Example value (replace with your own):

octocat

Repository

RequiredText

Name only, without the owner and without .git.

This input offers a picker for repository from your connected account. You can also supply its value directly.

Example value (replace with your own):

Hello-World

Pull Request Number

RequiredWhole number

The number shown in the interface.

This input offers a picker for pull request from your connected account. You can also supply its value directly.

Example value (replace with your own):

Verdict

OptionalChoice

Omit to leave the review pending.

Choices: APPROVE, REQUEST_CHANGES, COMMENT

Comment

OptionalText

Required for REQUEST_CHANGES and COMMENT. Markdown.

Example value (replace with your own):

Looks good to me.

Commit SHA

OptionalText

The commit being reviewed. Defaults to the latest one.

What comes back #

In the action editor, open Output → Returned Value to choose fields for your shortcut. These are the response fields described by the app; a service may omit an optional field or return an empty list. JSON File contains the full response.

Returned field	Type	Meaning
`id`	integer	Whole-number value.
`state`	string	APPROVED, CHANGES_REQUESTED, COMMENTED or PENDING.
`body`	string	Text value.
`html_url`	string	Text value.
`submitted_at`	string	Absent while the review is pending.
`commit_id`	string	Text value.
`user`	object	A group of named values.
`user.login`	string	Username.
`user.id`	integer	Whole-number value.
`user.html_url`	string	Their profile page.
`user.avatar_url`	string	Text value.
`user.type`	string	User, Organization or Bot.

Run it from Shortcuts #

Give the action a recognizable name and tap Save.
In Apple Shortcuts, add Shortcutify’s Execute Action and select the saved action.
Supply any Param or File slots you bound in the inputs, then run the shortcut.

If the result is unexpected, open Logs in Shortcutify, select the run, and inspect this step’s inputs and response.

Advanced reference #

Request, permissions, and identifiers

Request: POST https://api.github.com/repos/{owner}/{repo}/pulls/{pull_number}/reviews

Action identifier: github.pulls.reviews.create.v1

Permissions declared for this action: pull_requests:write. The account’s own access rules also apply.

Input	Request key	Location
Owner	`owner`	path
Repository	`repo`	path
Pull Request Number	`pull_number`	path
Verdict	`event`	body
Comment	`body`	body
Commit SHA	`commit_id`	body

GitHub API reference