Commit Days / Week Report

Last updated: October 27, 2026

Commit days / week shows how many days a week a typical active contributor commits code or has a pull request (PR) merged. It measures how consistently people code, not how much code they write.

Why it matters

  • Coding consistency: low values can mean time lost to meetings, support, or other non-coding work.

  • Work patterns: compared with Commits / week, it shows whether people code steadily or in concentrated bursts.

  • Onboarding: new hires usually start low and rise as they ramp up.

How it works

Commit days / week = commit days ÷ active contributor-days × 7

  1. For each person and calendar day, in your organization's time zone, Span records whether they committed (by author time) or had a PR merged (by merge time).

  2. Numerator: person-days where the person is marked Contributor, wasn't out of office (OOO), and had a commit or a merged PR. Ten commits in one day still count as one day.

  3. Denominator: active contributor-days, the days a person is marked Contributor, wasn't OOO, and had any code activity (commit, merged PR, PR review, or PR comment) that day or in the 30 days before it. Weekends count.

  4. Span divides and multiplies by 7. The value shows to one decimal place, and the maximum is 7.

Where to find it: Insights > Productivity > Velocity > Delivery, team and person Metrics tabs, custom reports, and custom dashboards, with percentile ranks.

Setup

  1. Connect your version control system.

  2. Mark people who don't write code as Non-contributor in Settings > People management.

  3. Connect an OOO source (calendar or HRIS) so time off leaves both sides.

Things to know

  • Weekends count, so a weekday-only coder tops out at 5. Worked example: an engineer commits on Monday, Tuesday, and Thursday, and is active all 7 days of the week under the 30-day rule. Commit days / week = 3 ÷ 7 × 7 = 3.0. Someone who commits every weekday and never on weekends scores 5 ÷ 7 × 7 = 5.0.

  • A merged PR counts as a commit day even when the person made no commit that day.

  • Review-only days don't count in the numerator, but they keep the person active, so they count in the denominator.

  • OOO days leave both sides, so vacations don't lower the rate. With a calendar source, a weekday is OOO only when out-of-office events cover more than 4 hours between 8am and 6pm; a shorter block leaves a full day. With an HRIS source, every weekday inside an absence is OOO. If the engineer above took Friday off with an all-day out-of-office event, Friday leaves the denominator: 3 ÷ 6 × 7 = 3.5.

  • Ignored repositories still count here. A commit in a repository you ignore for other metrics still makes a commit day.

  • Time zones: Span uses one organization time zone. GitHub's contribution graph uses each user's time zone, so late-night commits can land on different days.

  • Values close to 7 mean people commit most days including weekends. That can be worth a conversation about work-life balance.

  • Use it for patterns, not performance reviews. Low values can reflect architecture work, mentoring, or incident response.

Related articles

How to read Span's "/ week" metrics

PRs Merged / Week

Focus Time

OOO Person-Days

Need help?

Contact your Span account team or reach out to support@span.app.