How resolved findings are detected
Each time Qodo reviews a new commit, it re-evaluates every finding that’s still open against the changes made since the finding was raised.- Qodo looks at the full set of changes in the PR, not only the code the finding pointed to. A fix counts even when it lands somewhere else, for example in a new file or in a helper the finding did not mention.
- A finding is marked resolved when the changes address the issue it describes. Findings that the changes do not address stay open.
- When the full set of changes is not available, for example for a very large change set, Qodo checks the code the finding pointed to.
How resolved findings appear
A resolved finding keeps its title, struck through, followed by its status. It drops the other labels a finding usually carries, such as finding type, category, severity, or the ⭐ New mark. This keeps resolved findings in the background and makes the open, actionable findings stand out, which helps you focus on resolving them. Where the finding also has an inline comment, Qodo marks that comment as resolved, if your Git provider supports it.Placement
Resolved findings overflow
With resolved findings in their own section, the overflow setting controls how much of the section is shown.
Bitbucket and Gerrit do not support collapsible sections. As a result, resolved findings beyond the overflow breakpoint are not displayed. You can view them in the Qodo portal instead.
Hide resolved findings
Turn off Show resolved findings to leave resolved findings out of the review comment entirely, regardless of placement. Open findings count from 1.Configure resolved findings
Configure resolved findings in the Qodo portal (Recommended)
- Log in to the Qodo portal.
- Navigate to Configurations > Display > Resolved findings.
- Choose the options:
- Show resolved findings: Whether resolved findings appear in the review comment.
- Placement: Resolve in place, or Move to resolved section.
- Resolved findings overflow: How much of the resolved section is shown. Applies only when Placement is set to Move to resolved section.
- Click Save.
Configure resolved findings in .pr_agent.toml
resolved_overflow_count applies only when resolved_findings_placement is "resolved_section". For more information, see Configure Qodo using the .pr_agent.toml file.
Related resources
- Anatomy of a Qodo Code Review: The parts of the review comment and how to read them.
- Control findings visibility and expansion in pull requests: Set how many findings show before the rest collapse.
- Enable persistent review comments: Keep one review comment up to date across pushes.
- Customize the code review experience: What you can configure, and where to configure it.