Read the Overview
The Overview tab: flow metrics for the reporting window, one chart over every period, and where the work is happening.
On this page
Reports is where Limn measures how your team’s work flows. It opens on the Overview tab. The tab answers three questions for the workspace you have selected: how this window compares with the one before it, how the last few sprints or months compare with each other, and which repositories the work is in. Every figure is counted from your GitHub data. No AI writes or changes a number on this tab.
Reports covers every repository in the workspace. The repository picker on the Timeline does not narrow it. To measure a different set of repositories, switch workspace (see Workspaces). The tabs along the top are Overview, Chronology, Stories and, while AI is on, AI usage. Press 1 to 4 to switch between them.
#Flow metrics
The first block is Flow metrics. Its five tiles cover the workspace’s reporting window, which the heading names, for example This sprint so far or Last 14 days. Each tile compares the window with the earlier one named beside the heading. Select a tile to open the pull requests behind its figure. The picture below is a working model with made-up data: select a tile to try it.
- Merged: how many pull requests merged in the window.
- Time to merge: the median time from opened to merged, for pull requests merged in the window.
- Time to first review: the median time from opened to the first review, for pull requests opened in the window that have had a review.
- Checks green at merge: the share of merged pull requests whose checks were green when they merged.
- Time to fix red checks: the median time from checks going red to green again.
When either window has fewer than three pull requests behind a figure (or fewer than three fixes, for Time to fix red checks), the tile shows the earlier value, “was …”, instead of an up or down arrow. A small sample does not get a trend arrow.
Right now
Two tiles sit apart under Right now because they are not tied to the window. Open pull requests counts what is open at this moment, drafts not counted; select it to see the list. Red checks now counts open pull requests whose checks are red, with how long they have been red (counted from the pull request’s last commit).
Last 12 weeks
Under Last 12 weeks are weekly charts: Reviews and comments per merged pull request (people and bots drawn apart), Pull requests opened and merged and Time to fix red checks. Open More charts for the rest: failing checks, time to merge, checks green at merge, changes requested, review coverage (human-reviewed, bot-only and unreviewed merges), rework after review, time to resolve threads and time from review request to first review. These charts always cover 12 weeks, so they span more than one reporting window.
#Where the work is happening
Two cards show the same window, split by repository.
| Repository | Opened | Lines changed |
|---|---|---|
| acme/payments | 14 | 3.3k |
| acme/web | 11 | 2.1k |
| acme/api | 9 | 1.5k |
| acme/ledger | 5 | size unknown |
| Repository | Merged | Low | Medium | High |
|---|---|---|---|---|
| acme/payments | 0 | 4 | 2 | |
| acme/web | 2 | 0 | 3 | |
| acme/api | 3 | 1 | 1 | |
| acme/ledger | 0 | 1 | 0 |
- Activity by repository: pull requests opened in the window, split into those opened by people and those opened by automation, and the lines changed on them. Each column has its own scale, so compare bars down a column, never across the two.
- Reach by repository: every pull request merged in the window, by how far its change could reach: Low, Medium or High. This is the same estimate as the blast radius chip on a pull request, and it is a guess. The levels follow the sensitivity you set in Settings → Pull requests.
Both cards tell you what they leave out. A repository whose lines changed are not known says “size unknown” rather than showing zero. A pull request with no reach level yet is not drawn, and a line under the card says how many there are. When the list is cut, a line says how many repositories and pull requests are not shown, and how many repositories in the workspace had nothing in the window.
#Period reports
Period reports puts every completed period on one chart, one band per period, so you can see a trend rather than one comparison. The band for the period still in progress is hatched and shows a projection.
- Choose a Grain: Sprint (the last 12 weeks, at the workspace’s sprint length) or Month (the last 6 calendar months). Months have no projection, because they are not all the same length.
- Choose Show as: Change draws each metric as the change from its first period with enough data, so metrics of any size share one chart. Values draws the figures, one chart per unit.
- Select the metric chips to add or remove lines.
- Hover over or tap a band for its figures. Select a band to see its effort versus automation.
- Press the copy button to copy the periods as Markdown, for a sprint report or a wiki page.
The metrics include Merged PRs and, under it, …by people (merges without dependency bumps, code agents and release bots), Automation share of merges, Lead time, Time to first review by a person (bot approvals do not count), Merge CI success, PR size and its people-only twin, Review threads opened, Threads replied within 36h, Bot review comments, Human review comments, Bot comments per merged PR and Reviewer concentration (the share taken by the busiest human reviewer). A metric with too little data in every period says so, rather than drawing a flat line.
Effort vs automation
Below the chart, Effort vs automation splits the selected period’s merged pull requests, review comments and approvals by who did them: People, Code agents, Dependency bots, Limn, AI review, Quality gates & CI, Release automation and Housekeeping. Only the groups that did something are listed. Its headline is one number, for example “38% of merges were automated”, which tells you how much of the throughput above is people’s work.
#Why adding a repository does not move the lines
History is only as complete as the repositories Limn has been tracking. If you add three repositories in March, merges “go up” in March even though nobody worked faster. To stop that, every period is measured over the same repositories: the ones tracked since the first period shown. A line under the chip row says so, for example “4 of 6 repos: the ones tracked across every period.” The Effort vs automation panel counts all repositories and says so in its heading.
#Why it helps
Every figure on this tab opens the pull requests it counts, says which window it covers and says what it leaves out. You can quote a number in a retrospective and show where it came from. For where the time inside a pull request goes, read Chronology.