Deploy Frequency

What this report shows

Commits merged to `main` on the project repository, used as a proxy for deploy frequency (the project deploys on every merge). Reports show daily / weekly / monthly counts in a chosen window.

This is one of the DORA metrics — Deploy Frequency, Lead Time For Changes, Change Failure Rate, and Mean Time To Restore. Together they measure delivery performance.

How to read it

• Bars / counts per period — commits merged to `main` in that window.
• Lead-time stats — appear when commit data carries a deploy-live timestamp. Today the GitHub commit feed alone does not, so lead-time cells show "not available". This is a known gap, not a bug.

Industry benchmarks:

• Elite — multiple deploys per day.
• High — between weekly and daily.
• Medium — weekly to monthly.
• Low — slower than monthly.

Common questions

• Why doesn't this match my git log? The report counts `main` commits. Branch commits and rebased / squashed history can change the count vs what you see locally on a feature branch.
• Why is lead time "not available"? Lead time = time from commit to live deploy. We'd need each commit to carry a deploy-live timestamp. The current feed doesn't supply this.
• Why is today low? Today is in-progress; if "today" is bucketed by calendar day, the day isn't over.

What to do if numbers look wrong

1. Cross-check with `git log --oneline --since="<window>"` on a checkout of `main`.
2. If the count is impossibly high, look for a recent rebase / merge-of-many-commits — those count individually.
3. The GitHub API rate-limit can occasionally fail the data fetch — refresh the page after a minute.