Review and discuss changes
Open the pull request, read Files, and press + beside a line to add a line comment to your review. Review… sends your decision (Approve, Request changes or Comment) with a Summary and every line comment. Conversations can be replied to and resolved where the provider supports it.
Needs GitTree Pro or a running trial; Free keeps every local Git feature. Compare the plans.
On this page
Before you start
- GitTree Pro or a running trial: pull requests are part of Pro.
- The pull request is open in GitTree (Pull requests).
Where to find it
- In the pull request: Files, Conversation and Review….
| Action | macOS | Windows and Linux |
|---|---|---|
| Next change in the diff | F7 | F7 |
| Previous change | ⇧F7 | Shift+F7 |
Steps
Get the full diff
In Files, press Fetch Pull Request if asked. It writes the pull request’s head to
refs/ogt/pull/<number>; no branch, tag or working file changes.Comment on lines
Press + beside a line, write the comment and choose Add to Review. Your comments wait under Line comments for your review.
Submit the review
Press Review…, pick the Decision, write a Summary and press Submit Review. GitTree says Review submitted.
Expected result
Your review and line comments are on the provider, and the reviewer list shows your decision.
Discuss in the conversation
- Write under Conversation and press Comment, or Reply in a thread.
- Resolve closes a thread; Unresolve reopens it. Threads on code that has since changed are marked Outdated.
- After changes, Ask for Review Again… notifies the reviewers.
If something goes wrong
“Say what should change, or add a line comment.”
Request changes needs words: write a summary or add a line comment first.
“This provider does not offer the conversation here.”
Use Open in Browser to discuss it on the provider’s page.
Questions
Can I review my own pull request?
That is up to the provider; most do not let the author approve. GitTree shows what the provider answers.