Lead Time for Changes report from GitHub

Report on lead time for changes (PR opened → merged) from a GitHub export, tracked month by month against your own target. ReportInSite runs in your browser, so the file is read on your device and nothing is uploaded.

Try it with sample data Open the tool →

How to export it

Use the GitHub CLI. This measures pull request open → merge, a common stand-in for DORA lead time when deploys follow merges to main.

GitHub CLI

gh pr list --state merged --base main --limit 1000 \
  --json number,createdAt,mergedAt \
  --jq '["number","created","merged"], (.[] | [.number, .createdAt, .mergedAt]) | @csv' > prs.csv

Then open ReportInSite, go to the Data tab, choose Export from any app, pick Lead time for changes (PR opened → merged) and load the file. The recipe fills in the column mapping and the calculation; you can change any of it before importing.

What you get

This recipe feeds DORA › Lead Time for Changes. It rolls into the steering scorecard, the portfolio roll-up, trends and the PDF packs alongside every other source.

Steering scorecardThe value lands on DORA › Lead Time for Changes for each team, scored red / amber / green against your target.
Flow & DORA reviewShown as one of the four DORA keys, against your own target and with its trend.
Portfolio roll-upEvery team side by side on the heatmap, whichever tool each one uses.
TrendsDated rows fill earlier months, so the direction of travel is there from the first import.

Related reports

Every recipe, with export steps for each app, is in the Playbook under Data from any app. No recipe for your app? The custom mapper reads any CSV or Excel table.

Nothing to install, nothing to upload.

Try it with sample data All reports →