Skip to main content
When a pull request builds on earlier work or is part of a larger change, the review may need that background to understand the changes. If you link related pull requests in the description, Qodo uses them as additional context for the review.

​
How Qodo uses linked pull requests

Work is often split across several pull requests. For example, one pull request might introduce a backend change, while another adds validation or error handling. Without the context of related work, a review might flag something that has already been addressed elsewhere. When the pull request description links to other pull requests in the same repository, Qodo uses their titles, descriptions, and code changes as context for the review. This helps Qodo understand the intent and scope of the current pull request and avoid findings about work already covered in a related pull request. Linked pull requests can be open, merged, or closed:
  • An open pull request provides a snapshot of its code, which may change before it is merged.
  • A merged pull request provides context for changes that are usually already included in the current pull request’s base branch.
  • A closed, unmerged pull request provides context about the intent of the work, but its code is not assumed to exist in the repository.
Qodo reports findings only on the pull request being reviewed. Linked pull requests provide context only and are not reviewed or flagged themselves. To give Qodo additional context for a code review, reference a related pull request in the description of the pull request being reviewed. Qodo uses references to pull requests in the same repository automatically. References to pull requests in other repositories or to issues are not included. For context from another repository, see Cross-repository code review. You can reference a related pull request in either of these ways:
  • Paste its full URL, such as https://github.com/org/repo/pull/123.
  • Reference it by number, such as Depends on #123 or Follow-up to #456.
No additional setup is required.
Only pull requests in the same repository are used as context this way. Links to pull requests in other repositories, or to issues, aren’t included. For context from a related repository, see Cross-repository code review.