Skip to main content
Productivity metrics appear on Home, contributor/team views, and weekly digests. GitHub admins enable the modules in Settings → Workspace → Productivity Features and can limit them to specific teams.

​
Coding time

Coding time is an LLM estimate based on diff size, complexity, and author familiarity from git blame. It estimates coding only, excluding investigation, planning, meetings, and other contributions. Individual commits can be inaccurate; aggregate by contributor or week. For example, 8 estimated hours over two 8-hour workdays gives a score of 0.500. This is a model estimate of output, not a measurement of hours worked.

​
Attribution

Per-contributor metrics require a commit author email matching a verified email on the contributor’s GitHub account. Check both when a contributor is missing. Include external contributors in summaries and productivity metrics independently through Settings → Workspace → External Contributors. Excluded authors are omitted from metrics and commit processing.
If a contributor doesn’t appear in metrics:
  • Check that they’ve verified their email in GitHub settings
  • Ensure their Git config email matches: git config --global user.email "verified-email@company.com"

​
Email reports

Weekly digests include executive summaries, coding-time trends, and team activity. Configure recipients under Digest Emails and report boundaries under Weekly Cadence in workspace settings.