GitHub admins can toggle Productivity Features on/off in Settings → Workspace → Productivity Features, and optionally limit them to specific GitHub teams.
Accessing Productivity Insights
Email Reports
Macroscope sends a weekly digest with executive summaries, coding time trends, and team productivity insights. Manage recipients in Settings → Workspace → Digest Emails.Dashboard
The home page dashboard includes everything from the weekly reports, plus additional productivity trends and contributor-level activity like Clickety Clack Scores.Coding Time
An LLM-generated estimate of time spent coding, calculated per commit using diff size, change complexity, and author familiarity (via git blame). This estimates pure engineering time and does not reflect non-coding work (investigating, planning, meetings). Estimates may be inaccurate at the individual commit level but are useful when aggregated by contributor or week.Landed vs All Coding Time
The Home page and productivity views display two coding time metrics:- All: Total estimated coding time across all commits.
- Landed: Coding time for commits that have been merged to release branches.
Clickety Clack Score
A normalized productivity score: estimated Coding Time ÷ elapsed working hours. For example, 8 hours of estimated coding time over 2 work days (16 hours) = 0.500 Clickety Clack Score. This measures output per calendar hour against a baseline (the model’s understanding of an average engineer in your codebase). It doesn’t capture non-coding contributions like research, recruiting, or coaching.Attribution
Only verified contributors appear in per-contributor metrics. A contributor is verified when their commit author email matches a verified email on their GitHub account.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"