Working agreements

What it measures

Weekly adherence to the team's own agreements — review within N hours, max PR size, WIP limit, max PR age, and approval-before-merge — each as a percentage of PRs that met the bar.

Why it matters

These are the team's own rules, not git-pulse's. Tracking adherence turns informal norms into a visible, improvable signal the team set for itself.

How to read it

• Each agreement is a separate line; a value of 100% means every PR met it that week.
• Thresholds live in gitpulse.yml — set 0/false to disable any check the team hasn't agreed to.

Anti-blame

Breaches are listed without authors. The approval-before-merge check is trend-only — never drilled down — because that drill-down could re-identify people.

Common misreads

• Draft PRs cannot breach review-within or max-age — the clock starts when the author marks the PR ready for review; draft state is read at sync time (a whole-interval approximation).
• Drafts still count toward the WIP limit — they are active work, just not yet reviewable.
• When size scaling is configured, the review-within and max-age thresholds stretch for larger PRs (e.g. XL PRs get a multiple of the base window) — so a big change isn't unfairly flagged. The breach drilldown shows each PR's size-specific cap.