Outcomes

An outcome is a devlo review comment whose recommendation made it into the merged code, tagged with the kind of problem it prevented.

Where to see them

• Overview shows outcome tiles for the last 4 weeks across your organization.
• Contribution > Performance shows the same tiles for the date range and repository you pick.

Select a tile to see the comments behind it, each with its pull request and diff.

Only owners and admins see outcomes, in the app or by asking the Assistant.

How devlo records an outcome

After a pull request merges, devlo checks whether each recommendation is in the merged code, from a quick fix or by hand. If an applied recommendation prevented a specific problem, devlo records it as an outcome of that type. Others count only in Recommendations Applied on Performance.

Outcome types

Tile	What it counts
Security risks averted	Vulnerabilities, privacy, and compliance issues
Downtime instances prevented	Problems that would cause downtime or failed deploys
Logic errors fixed	Incorrect behavior and logic bugs
Performance hits saved	Latency, throughput, scalability, or cost problems
UX issues fixed	UI glitches, accessibility, and other user-visible quality issues
Data integrity issues fixed	Data corruption, loss, or inconsistency
Observability gaps fixed	Missing logs, metrics, traces, or alerts
Test coverage gaps fixed	Missing or flaky automated tests
Tech debt avoided	Long-term maintainability and code quality concerns
Other	Anything else a recommendation prevented

When there are no outcomes

Usually the pull requests are still open, or the team didn’t apply the recommendations. If few recommendations get applied, customize reviews.

Related

• Performance
• Overview
• Quality