Data
Measure delivery from git
DORA metrics computed from real history, with what they actually mean.
Fill it in
Where the history is.
How far back.
days
What the numbers cannot tell you.
Your prompt
Compute delivery metrics for [the repository], over 180 days. Deployment frequency, lead time for change, change failure rate and time to restore, derived from what the history can actually support. Say how you derived each one: a repository without deploy markers cannot give you deployment frequency, and inventing a proxy without labelling it is how a dashboard becomes fiction. Show the DISTRIBUTION, not the average. Lead time is heavily skewed, and a mean of four days made of mostly-two-hours plus a handful of month-long PRs describes nothing that happens. State what the numbers cannot tell you, prominently. These metrics are trivially gameable, and a team measured on them will produce better numbers without producing better software.
Use Measure delivery from gitOpens with everything above already filled in.
Why this works
A repository without deploy markers cannot give you deployment frequency, and inventing a proxy without labelling it turns a dashboard into fiction. This says how each number was derived, shows distributions rather than means, and states what the metrics cannot tell you.