GitHub PR review context
When you finish a pull request review in GitHub, you choose how that review is submitted. For AI Library Upgrade, only one of those choices starts an improvement cycle in CodeLogic.
Review type and the improvement cycle
In GitHub’s Finish your review dialog, the three submission options behave differently with CodeLogic:
| GitHub option | Effect on CodeLogic |
|---|---|
| Comment — general feedback without explicit approval | Does not trigger an improvement cycle. |
| Approve — approve merging these changes | Does not trigger an improvement cycle. |
| Request changes — feedback suggesting changes | This is the only option that triggers an improvement cycle. |
Use Request changes when you want CodeLogic to treat your review as a signal to run the improvement flow (for example, to iterate on AI-assisted fixes using your feedback). Submitting Comment or Approve will not start that cycle.
Context used for AI prompting
Separately from the improvement cycle, CodeLogic can still incorporate pull request review context into AI prompting—together with the PR title, description, and issue comments—so reviewers’ inline feedback and discussion can inform ticket generation and implementation guidance.
What can be included
- Pull request metadata (title and body)
- Issue-style comments on the PR
- Pull request review comments (inline review threads)
For how to shape PR descriptions and comments for best results, see Custom Prompting.
GitHub configuration
If you use repository webhooks (instead of or in addition to the CodeLogic GitHub App), ensure the webhook is subscribed to the review-related events GitHub offers for pull requests, including Pull request review comments, Pull request reviews, and Pull request review threads, as described in Configuring GitHub Webhooks.
That keeps Change Requests and related PR-driven workflows aligned with activity on the pull request, including review discussion.