Skip to main content

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.

AlphaGitHubGitLabBitbucketAzure DevOps
Available to single-tenant customers on all plans. Currently in early access and being gradually rolled out to all customers.
Every time Qodo reviews a pull request, it generates findings: issues identified in the code such as bugs, security vulnerabilities, rule violations, or requirement gaps. The Findings page in the Qodo portal tracks these centrally across all your repositories, giving team leads and engineering managers visibility beyond individual reviews. Review the table to track whether critical issues are being resolved before merge, identify repositories with recurring problems, and measure the effectiveness of your review standards. To access the Findings page, go to the Qodo portal and select Findings from the left navigation menu.
Findings page showing analytics cards and the findings table

​
How to interpret findings

Start with the analytics cards to get a picture of trends over the last 30 days, then use the findings table to drill down by repository, PR, action level, or category. Focus on:
  • Findings merged without resolution, to identify where standards enforcement needs tightening.
  • Recurring findings across repositories, to spot systemic issues that may warrant a new rule or team-wide guidance.
  • Resolved critical findings, to validate that the review process is working as intended.

​
Best practices

  • Start with the big picture: Check the analytics cards before drilling into individual findings, and filter the table by action level to focus on what matters most.
  • Look for patterns, not just volume: The same finding type appearing across multiple repositories usually signals a systemic gap in team practice rather than an isolated issue.
  • Use findings to iterate on your rules: Routinely ignored findings or rising bypass rates are a signal that your governance configuration needs adjustment. Refine the rule rather than accepting the noise.

​
Additional resources