Function run_lead_time
pub fn run_lead_time(db: &FactsDb, opts: &Options) -> Result<Vec<LeadTimeRow>>Expand description
Run the lead-time analysis. Returns commits ordered by
lead-time DESC. Merge commits are excluded — their lead-time is
architecturally zero on most workflows.
§commits.date vs commits.committer_date semantics
commits.date is the author date (when the commit was first
authored — git commit’s %aI); commits.committer_date is when
it last entered mainline (%cI). On linear-history workflows
(rebase, squash) these are often equal — the squash commit is born
at merge. On merge-via-merge-commit + review workflows the delta is
the true in-flight review time.
§Errors
Returns CodeLoreError::Analysis on DuckDB errors.