Review a pull request
Read a pull request, inspect its files and checks, and continue review actions on GitHub.
What you'll have
A pull request inspected by its head commit, changed files, checks and review status.
Review shows the repository connected to the channel. A pull request number identifies a change within that repository.
Select Review from the channel’s Switch surface menu. Check the repository name before choosing a pull request.
Result Review shows the connected repository and its pull requests.
Choose open, closed or all pull requests. Use the search and filters to narrow the list. Select Load more when more results are available.
Result The list shows the matching pull requests from the loaded pages.
Select a pull request. Read its head commit, target branch, reviewers and merge status. A reviewer count without individual names does not identify each person’s decision.
Result The pull request opens as a page with its description, branches and review status.
Select a file in Files changed. Read its change status and patch. Check for a missing or shortened patch before treating it as the complete change.
Result The selected file's diff appears with additions and deletions.
Read the checks beside the change. Follow a check’s details link to inspect a failure. A passing check does not replace a review of the code.
Result The checks show their reported states and links to further details.
Use the GitHub link for comments, thread replies, approval, requested changes or merging. Check the pull request number and head commit there before acting.
Result GitHub opens the same pull request for review actions.
If this doesn't work
If Review reports no connected repository, check the channel’s repository connection. An inactive connection needs attention before another read can work. For a failed read, use Try again when it becomes available. Refresh requests another read; it does not guarantee that a check has finished. If the head commit changes while you read, refresh before continuing the diff. Binary files and large patches can require inspection on GitHub.
The review covers the head commit you inspected. New commits require another look at the diff and checks.
Fill an empty description section
An empty description, test plan or acceptance criteria section can offer a Forge draft. Generate the draft, read and edit it, then choose Save to send it to the pull request. Discard removes the proposal without saving it. A generated draft is not a posted review or an approval.
If a save reports an unknown outcome, inspect the pull request on GitHub before sending again. If you cannot access the repository, check the repository connection and your permissions. Keep the proposal until you know whether the save reached GitHub.