Skip to main content
BetaGitHubGitLab
Support for additional Git providers is coming soon.
PR history indexing is a core capability of the 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 indexing 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 indexing 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.

​
How PR history indexing works

Before Qodo can use a repository’s PR history, it indexes that history in the background. The initial indexing run is triggered by the first pull request opened on the repository after it connects to Qodo, not automatically at connection time, then continues incrementally as new pull requests are merged. Check a repository’s indexing progress, and which features it currently unlocks, on the Manage repositories page.

​
Continuous learning

PR history indexing 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 indexing powers

PR history indexing 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 for how to read it.
  • In governance rule generation: Recurring patterns across your pull request history are mined into enforceable rules. See Rule Miner for how that works.