> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding PR history

> PR history is a core capability of the Context Engine, Qodo's mechanism for learning from your team's pull request activity to judge what actually matters in a review.

<div style={{ display: "flex", alignItems: "center", gap: "6px" }}>
  <Badge color="outline-purple" size="sm" shape="pill">Beta</Badge>
  <Badge color="outline-provider" size="sm" shape="pill" icon="github">GitHub</Badge>
  <Badge color="outline-provider" size="sm" shape="pill" icon="gitlab">GitLab</Badge>
</div>

<Note>Support for additional Git providers is coming soon.</Note>

PR history is a core capability of the [Context Engine](/core-concepts/context-engine), Qodo's knowledge layer. It indexes and analyzes pull request activity across the repositories connected to Qodo, transforming those repositories from static snapshots into an evolving record of how your team actually reviews and ships code. Qodo uses this record to judge whether something is likely to matter to your team, rather than relying only on generic best practices.

## Why PR history matters

AI code review tools often surface many findings, but it can be difficult to know which ones are genuinely important for a specific repository. Without historical context, automated reviews typically suffer from:

* **Disconnected suggestions** that don't reflect a team's actual standards
* **Invisible past decisions**, causing the same suggestions to resurface repeatedly
* **Low signal-to-noise ratio**, making it harder to identify what truly matters

PR history addresses this by analyzing how similar issues were handled in the past, so Qodo can distinguish between a pattern your team actively enforces and one that's already been considered and dismissed.

## How it works

When reviewing a pull request, Qodo analyzes past pull requests with similar findings and code patterns, along with the comments, discussions, and outcomes that followed. This helps answer questions such as:

* Is this issue actually important for this repository?
* Does your team usually fix this type of finding?

Based on how similar findings were handled previously:

* If similar issues were usually fixed, Qodo treats the new finding as likely relevant.
* If similar issues were often dismissed, Qodo indicates that the finding may not require attention.

## Continuous learning

PR history isn't a one-time snapshot. Qodo evolves with your codebase, learning from accepted suggestions and pull request comments to stay aligned with how your team's standards change over time. As new pull requests are merged and new review decisions are made, Qodo's understanding of what matters updates with them, so relevance judgments stay current instead of drifting out of date.

## What PR history powers

PR history is a core capability of the Context Engine that powers other parts of the platform:

* **In code review findings:** Every finding gets a relevance classification based on how similar issues were handled in the past. See [Relevance](/code-review/relevance) for how to read it.
* **In governance rule generation:** Recurring patterns across your pull request history are mined into enforceable rules. See [Rule Miner](/governance/rule-enforcement/rule-miner) for how that works.

## Related resources

* [Understanding the Context Engine](/core-concepts/context-engine): See how PR history fits alongside codebase and organizational context as a source Qodo reasons over.
* [Qodo platform core capabilities](/core-concepts/qodo-platform-core-capabilities): See where PR history fits among the platform's other capabilities.