GitComet Pro Review
Review
Review pull requests, branches, and uncommitted work in GitComet Pro file by file. Marks remember the content you read, discussions sync with the forge, and Finish review posts your decision.
Review lets you read a change file by file in GitComet's own file list and diff view, and remembers what you have read. Open it with the Review tab beside History.
Review reads the change from your local Git repository. Reviewing never stages, commits, or merges anything.
The review queue
Review opens on the queue of things you can review:
- Pull requests on your forge, for an approved repository with a forge connection;
- In progress, the reviews you have started;
- Branches ahead of the base branch;
- Uncommitted work: the Working tree (staged, unstaged, and untracked changes against
HEAD) and each of your Linked worktrees; - Review a branch or range, to compare any base and head. The comparison starts where the head left the base.
The Needs attention and Changed since review filters narrow the queue. A review with New commits since you read it or New commits since you finished shows that too.
Read and mark files
Select a file to see its diff. Mark each file as reviewed when you have read it. A mark records the content you read: if the file changes afterwards, it needs review again.
On GitHub, files you mark as viewed also sync to the pull request. On other forges, marks stay on this device.
| Key | Action |
|---|---|
J | Next file |
K | Previous file |
R | Mark the file reviewed, or not |
U | Mark the file unreviewed |
C | Comment on the selected lines |
E | Show the checks |
Esc | Back to the queue |
? | Show these keys |
The same actions are in the command palette under Review:.
Inspector tabs
The Details panel has these tabs for the open review:
- Discussion: the pull request's comment threads. Reply, resolve, edit, and delete comments, and add your own on selected lines. Comments whose lines have changed are marked Outdated.
- Context: what the change is about and where to start, related files, and the owners of the selected file.
- Evidence: the pull request's Checks and their Annotations.
- Impact: the selected file's neighbourhood, such as new calls, callers, and related tests.
- Hotspots: how often the changed code has changed recently.
- Activity: further actions the forge offers for the pull request, such as its notifications.
Finish a review
Choose Finish review. GitComet Pro shows how many files you have not reviewed yet, how many threads are open, and how many draft comments it will post. Choose Comment, Approve, or Request changes, then Finish review to post your review and its draft comments to the forge.
For a branch, a range, or uncommitted work there is nothing to post, so the button says Record decision and the decision stays on this device.
Stacked pull requests
When a pull request is part of a stack, Review shows the related pull requests and offers stack maintenance such as Rebase stack…, Merge bottom PR…, and Open next PR.