app/review.md +35 −7
412. Hover the line you want to comment on.412. Hover the line you want to comment on.
423. Click the **+** button that appears.423. Click the **+** button that appears.
434. Write your feedback and submit it.434. Write your feedback and submit it.
44445. Once you are done with all your feedback, send a message back to the thread.5. After you finish leaving feedback, send a message back to the thread.
45 45
4646Because the comment is anchored to a line, Codex can usually respond moreBecause comments are line-specific, Codex can respond more precisely than with a
4747precisely than with a general instruction.general instruction.
48 48
4949Inline comments are treated as review guidance. After leaving comments, send aCodex treats inline comments as review guidance. After leaving comments, send a
50follow-up message that makes your intent explicit, for example “Address the50follow-up message that makes your intent explicit, for example “Address the
51inline comments and keep the scope minimal.”51inline comments and keep the scope minimal.”
52 52
55If you use `/review` to run a code review, comments will show up directly55If you use `/review` to run a code review, comments will show up directly
56inline in the review pane.56inline in the review pane.
57 57
5858<CodexScreenshot
59 alt="Inline code review comments displayed in the review pane"
60 lightSrc="/images/codex/app/inline-code-review-light.webp"
61 darkSrc="/images/codex/app/inline-code-review-dark.webp"
62 maxHeight="400px"
63/>
64
65## Pull request reviews
66
67When Codex has GitHub access for your repository and the current project is on
68the pull request branch, the Codex app can help you work through pull request
69feedback without leaving the app. The sidebar shows pull request context and
70feedback from reviewers, and the review pane shows comments alongside the diff
71so you can ask Codex to address issues in the same thread.
72
73Install the GitHub CLI (`gh`) and authenticate it with `gh auth login` so Codex
74can load pull request context, review comments, and changed files. If `gh` is
75missing or unauthenticated, pull request details may not appear in the sidebar
76or review pane.
77
78Use this flow when you want to keep the full fix loop in one place:
79
801. Open the review pane on the pull request branch.
812. Review the pull request context, comments, and changed files.
823. Ask Codex to fix the specific comments you want handled.
834. Inspect the resulting diff in the review pane.
845. Stage, commit, and push the changes to the PR branch when you are ready.
85
86For GitHub-triggered reviews, see [Use Codex in GitHub](https://developers.openai.com/codex/integrations/github).
59 87
60## Staging and reverting files88## Staging and reverting files
61 89
62The review pane includes Git actions so you can shape the diff before you90The review pane includes Git actions so you can shape the diff before you
63commit.91commit.
64 92
6593You can stage, unstage, or revert changes at multiple levels:You can stage, unstage, or revert changes at these levels:
66 94
67- **Entire diff**: use the action buttons in the review header (for example,95- **Entire diff**: use the action buttons in the review header (for example,
68 "Stage all" or "Revert all")96 "Stage all" or "Revert all")
72Use staging when you want to accept part of the work, and revert when you want100Use staging when you want to accept part of the work, and revert when you want
73to discard it.101to discard it.
74 102
75103### Partially staged states### Staged and unstaged states
76 104
77Git can represent both staged and unstaged changes in the same file. When that105Git can represent both staged and unstaged changes in the same file. When that
78happens, it can look like the pane is showing “the same file twice” across106happens, it can look like the pane is showing “the same file twice” across