ActionGitHubUpdated September 2026
How do I submit a review on a GitHub PR?
Short answer: You can submit pr review in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub Submit PR Review action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Owner owner | string | Required | GitHub repository owner — the user or organization login (the part before / in owner/repo URLs). |
Repository repo | string | Required | GitHub repository name — the part after / in owner/repo URLs. Not the full URL. |
PR Number pull_number | number | Required | GitHub pull request number — the integer shown after /pull/ in the PR URL (per-repo, not global). |
Review Action event | options | Required | Review Action. Options: Approve, Request Changes, Comment |
Review Comment body | string | Optional | Message body content. Plain text unless the API specifies HTML/markdown. |
Sample request
{"owner": "e.g. octocat","repo": "e.g. hello-world","pull_number": "e.g. 137","event": "{{trigger.event}}","body": "e.g. Hi there, thanks for reaching out."}
Returns
{"id": 80,"body": "LGTM!","user": {"login": "octocat"},"state": "APPROVED"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Submit PR Review.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Submit PR Review.
What does the Submit PR Review action do in GitHub?
Submits a review on a GitHub pull request: APPROVE, REQUEST_CHANGES, or COMMENT. Used for AI code review or for cross-system approval gating.
What inputs does Submit PR Review require?
Required: Owner, Repository, PR Number, Review Action. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if GitHub returns an error?
The run history shows the failed step with its input and the error message GitHub returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Submit PR Review support batch operations?
Run Submit PR Review inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GitHub's rate limits.
More actions
Other GitHub actions.
Action
Add Labels
Adds labels to a GitHub issue or pull request by name. Used for AI-driven triage or auto-tagging based on file paths touched.
ActionCreate Comment
Adds a comment to a GitHub issue or pull request. Used for AI review summaries, build-status pings, or status broadcasts from CI/CD.
ActionCreate Issue
Creates a new issue in a GitHub repository with title, body, assignees, labels, milestone, and project. The default write for piping bug reports or alerts into GitHub.
ActionCreate Pull Request
Creates a new pull request in a GitHub repository from a head branch to a base branch with title, body, and draft flag. Used for auto-PRs from generated code or dependency updates.
ActionCreate Release
Creates a new release for a repository with tag name, target commitish, name, body (release notes), draft, and prerelease flags. Used to automate releases from your CI pipeline.
ActionCreate or Update File
Creates or updates a file in a GitHub repository in a single commit, with branch, commit message, and content. The SHA is auto-fetched on update; the standard tool for small file commits without a full git client.