Code review

Your session's changes

Show changes (View ▸ Show Changes, /diff, or a click on the pill over the prompter that says what changed, such as Changed 3 files) opens Changes in the side panel: what changed in the session's checkout, in the same words, and under them the branch, any conflicts to resolve, the commits to push or pull, and the line counts.

• When more than one kind of file changed, they're grouped as Documents, Images, Media, Data, Code and Other files. Each file says what happened to it, such as New, Edited, Deleted or Renamed from ….
• A picture shows before and after. A document, picture or media file opens rendered in Documents, and its chevron shows the lines that changed. A code file opens to its diff, where every line is marked with a sign as well as a colour.
• Stage and Unstage each file, or Stage all and Unstage all.
• Write a message and choose Commit only, or Commit, push & PR ⌘↩ to push the branch and open a pull request.
• Request review starts a read-only reviewer session over the checkout. Its verdict lands back in Changes.
• History lists the checkpoints taken in this checkout, to restore any of them (see Sessions).

The card at the end of a turn that changed files has Review, which opens the changes of that turn alone. Show all changes goes back to the whole checkout.

Pull requests

Code review on the rail lists GitHub pull requests in three groups: Authored by me, Needs my review and Needs my team's review. Search the list, or paste a pull request's link into the search to open it. Pin one to keep it at the top.

Realm reads GitHub through your own gh, the GitHub command line, signed in as you. Realm holds no GitHub token of its own and sees what gh sees.

Set up GitHub

Until gh is installed and signed in, the page says what's missing and offers Set up GitHub, which opens a terminal with the command typed in for you to run. Coming back to the window checks again.

brew install gh && gh auth login

Press Return to run it and sign in when it asks. No Homebrew? gh is also at cli.github.com.

Review with an agent

1. Open a pull request. Summary shows its description, checks, merge status, reviewers and comments; Changes shows its diff, with a file tree and one-column or side-by-side views.
2. Press Review with and the model's name. The chevron beside it sets the model and Tell the reviewer how to review your code: instructions every review in your profile follows.
3. The reviewer's summary and findings appear under Review by and the model. Each finding has Add to review, or Add to my comment when it isn't on a changed line. Open session shows the review's whole trace.
4. Add line comments of your own on the Changes tab.
5. Press Submit review, choose Comment, Approve or Request changes, write the review comment (it's required), and post it with ⌘↩.

Ask about a pull request

The prompter at the foot of a pull request asks about it. The chip beside it, named for where it asks, chooses the space, and the first question starts a session there with the pull request attached. Its answers show beside the pull request, and Hide answers folds them away.