Skip to main content
Review Insights turns your merged pull requests (PRs) and merge requests (MRs) into team-level numbers: who shipped what, how clean it was at merge, and which kind of finding keeps coming back. Use it in a weekly team review or a 1:1 to pick one thing to coach, then click through to the findings behind each number.

​
Prerequisites

  • Review connected to at least one repository, with some merged PRs or MRs. See Review setup.
  • Any workspace role (Admin, Developer or Viewer) to view Insights. Changing the report schedule needs the workspace Admin role. See roles.
  • For the Review Patterns tab: the review mode set to Advanced or Auto, because that tab counts only Advanced Reviews. With Auto, only the changes Auto sends to an Advanced Review count. See review modes.
Everyone with a workspace role, including Viewers, can see the leaderboard with developer names, and there’s no setting to hide it. Check this with your team before you roll Review out.

​
Open Insights

1

Go to Insights

Click Review in the left navigation, then Insights. The page header reads Quality trends, patterns and contributions.
2

Pick a date range

Open the Date range menu in the top right. Ranges come in two groups:Weeks start on Monday at 00:00 UTC. This Week has no trend, so it hides the Details and Review Patterns tabs. Pick a longer range to bring them back.The range is the only filter. Insights always covers every repository in the workspace. For one repository’s view, use its PDFs in the Reports tab.
3

Pick a tab

Success state: summary cards load at the top of Leaderboard and Details, and the tab you picked shows data for the range.
The tab, range and metric live in the page URL, so you can bookmark a view or paste it into a team channel and others see the same thing. Insights has no CSV or API export. Share the URL, or the report PDFs from the Reports tab.

​
Summary cards

Leaderboard and Details open with four cards for the selected range: A strip under the cards adds up to three signals, each shown only when there’s data for it: No votes in the range means no accurate findings signal, rather than 0%. Ask your team to vote on findings if you want this number.

​
Leaderboard

The Developer Leaderboard ranks developers “by contribution and quality, as scored at merge”. Scores are frozen when a change merges, so later edits to findings don’t move past rankings. Bot authors are left out of every Insights number. Review spots them by username: a GitHub [bot] suffix, a trailing -bot, _bot or .bot, or a GitLab project or group access-token user. A service account with any other name is counted, and you can’t exclude accounts from the workspace.

​
How the scores are built

For example, a developer with a Quality Score of 8 on a team averaging 7, and a total Impact of 300 against a team average of 200, scores (1.14 + 1.50) ÷ 2 = 1.32. Use the leaderboard to spot who to support and what to coach, not as a performance rating: Impact measures size, not value.

​
Details

Details charts one metric per developer over the range, then lists each week or month in a table.
  1. Choose the metric from the Metric menu: Contribution Score, Quality Score, Changes or Total Impact.
  2. Read the chart titled, for example, Quality Score by Developer.
  3. Scroll to the table for the team totals per week or month: Merge Requests or Pull Requests, Team Quality, Total Impact, Findings and Authors.
Use it to check whether a dip is one bad week or a trend.

​
Review Patterns

Review Patterns is the coaching view. For each developer it shows how often their reviewed changes merged without a finding in each of four domains:

​
What counts

Only finished, non-draft Advanced Reviews on changes with a recorded outcome count. Fast Reviews, unfinished reviews, pipeline findings and bot authors are left out. If nothing qualifies, the tab shows No confirmed Advanced Reviews in this period. A domain rate is:
A change counts once per range, even if it was reviewed several times. Several findings in one domain still count that change once. Resolved and open findings count the same, and severity never weights a rate.

​
Main coaching priority

The top of the tab names the domain with the highest team-wide share of affected changes. On an exact tie, Critical and High finding counts break it. If they tie too, every tied domain is listed.

​
Explore the evidence

1

Select a cell

Click a developer’s cell in a domain column.
2

Read the trend

A Weekly trend or Monthly trend chart shows that developer against the pooled Team line.
3

Open the findings

The evidence table lists each finding with Severity, Finding, Location, Review and Status (Open or Resolved). Click Load more evidence for older ones, and follow the Review link to the change.Success state: you can name the specific findings behind a rate before you bring it up with the developer.
A resolved finding stays in the evidence. It still shows what the review caught.

​
Thin data

​
Reports

Reports gives each repository two PDFs each week: a Technical PDF for engineers and technical leads, and a Product PDF for product and engineering leaders. Rows are grouped by period, with one row per repository showing Repository, Generated, Trends, Actions, Status and PDFs. The date range control is hidden on this tab.
1

Choose how reports run

Turn on Scheduled reports to generate them every Monday from 09:00 UTC (each workspace starts within 30 minutes of that). Click Generate now for a run today. Changing the schedule needs the workspace Admin role.
2

Read a report

Open a row to see the Repository report panel. It shows Trends, such as “Findings down”, and Tracked actions: actions from this and earlier reports, each marked open, improved, resolved, regressed or stale. The row also shows the repository’s health: Healthy, Watch or At risk, with a score out of 10, or Not rated yet.
3

Download the PDFs

Download the Technical PDF or Product PDF from the panel or the row. A failed row offers Retry.
Until the first run, the tab shows No reports yet. After a scheduled run, workspace admins get a Reports ready notification. Turning the schedule off keeps existing reports. Review also sends a separate Weekly Review digest email of the week’s review activity. Manage both under Review in notification settings.

​
Troubleshooting

This Week is selected, and it has no trend. Pick Last 4 Weeks or longer in Date range.
Your changes were reviewed in Fast mode, or none finished in the range. Go to Review → Settings, and in the Review section set Review mode to Advanced or Auto. Then check back once new changes merge. Earlier Fast Reviews never appear here.
They have fewer than 3 reviewed changes in the range. Widen the range, or read the Team rate instead.
Insights counts merged changes only. Open PRs and closed-without-merge PRs don’t appear, and neither do bot authors. Check the PR merged inside the selected range.
Your account doesn’t have Review view permission in this workspace. Ask a workspace Admin to check your role and membership. See roles.
Click Retry in that panel. Your range and tab stay selected.

​
Next steps

Learnings

Turn the domain your team keeps missing into a rule every review applies.

Review workspace

Open the changes behind a number and settle their findings.