Review pull requests in Riff
A colleague has changed the checkout calculation. Open the request in Riff to read its description, compare the files, discuss a line and make a review decision against the version you inspected. GitLab calls these requests merge requests; the workflow below applies to them too.
Open the version to review
- Connect the Git host with an account that can access the repository and perform the intended review action.
- Open Pull Requests in the repository tab and choose a request, or use Review in Riff from Setlist.
- Read the description, author, reviewers, source and target branches, and the reviewed commit SHA. Select a changed file to inspect its diff.
- Check Discussions for existing feedback and Checks for the provider's reported results. A missing or partial result is not a successful check. Open the request at the provider when Riff indicates incomplete coverage.
The request can be available while its diff is not. Refresh the review or open a local clone so Riff can prepare the exact revisions when needed. Binary files, very large diffs and files renamed without text changes may have no commentable text.
Discuss a line or reply
Use Comment on lines, select a line in the loaded diff and write the comment. The composer identifies the file and line before you send. To reply, select an existing discussion and write in its composer. Comments are sent to the provider when you select Send comment.
The line list displays at most 4,000 lines and shortens long line previews. Use Diff for the richer comparison and the provider's page for content outside Riff's loaded view. An unavailable resolution status means the provider did not supply that information; it does not mean a thread remains unresolved. GitHub's current review connection does not report resolution status.
Approve or request changes
| Provider | Decisions available in Riff |
|---|---|
| GitHub | Approve or request changes. A review message is required when requesting changes. The submission identifies the reviewed commit. |
| GitLab | Approve the reviewed commit. Requesting changes is unavailable in this integrated flow; leave a comment or use GitLab for other review actions. |
| Bitbucket Cloud | Approve or request changes. The provider cannot bind the decision atomically to a commit. |
| Azure DevOps Services | Approve or request changes, represented by the provider's vote that waits for the author. The provider cannot bind the vote atomically to a commit. |
Check the commit SHA in the confirmation before submitting. Riff checks the request again around submission. If it changed, review the new version before making another decision. Provider permissions and branch policies still apply; an approval does not merge the request.
Read the submission result
If Riff reports that the action was sent to an earlier version, it was sent, but the request changed. If it reports that the latest revision could not be checked, submission succeeded but the follow-up check is unavailable. Refresh before proceeding in either case.
If the operation could not be confirmed, inspect the provider and refresh before retrying to avoid duplicate comments or votes. Riff does not automatically repeat an uncertain submission. Drafts remain in the current review session, and closing the context or window waits while a submission is in progress.
Try the reviewed code
Choose Open in worktree, select a separate destination and review the branch name. Riff prepares the exact reviewed commit while preserving the original checkout. Run the project's checks there, then return to the review. Work contexts and worktrees explains switching tasks and safely removing the additional folder. Riff's review flow does not require AI.