Skip to main content

​
Key Concepts

Clickity Clack Score

A normalized productivity metric calculated as coding time ÷ working hours

Coding Time

LLM-generated estimate of time spent coding, calculated per commit

Top Contributors

Highlights contributor stats such as number of commits and estimated coding effort
GitHub admins can toggle Productivity Features on/off in Settings → Workspace → Productivity Features. To only show Productivity Features for specific GitHub teams, admins can select the teams they’d like to have the functionality enabled for.
Home

​
Accessing Productivity Insights

Weekly reports are sent via email and provide high-level updates. These reports capture coding time trends over the last six weeks, engineering output by project, and insights into team productivity.
Add or remove weekly email recipients in Settings → Workspace → Digest Emails.
The dashboard on the home page of the Macroscope website includes everything from the weekly reports and adds deeper visibility. On the dashboard, you’ll find additional productivity trends, project details, and contributor-level activity (e.g. Clickity Clack Scores).

​
Understanding Coding Time Estimates

Coding Time is 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 time spent on non-coding tasks (e.g. investigating, planning, architectural meetings, etc). As with other LLM-generated content, Coding Time estimates may be inaccurate and may not reflect actual time spent doing engineering work when assessed at the commit level. We believe this estimate is a helpful and relatively accurate measure when aggregated (by project, by week).

​
Attribution in Per-Contributor Metrics

Only verified contributors appear in per-contributor metrics (e.g. Top Contributors list). A contributor is verified when their commit author email address can be linked to a GitHub account. This verification process is how Macroscope attributes commits to specific GitHub users, which is how Macroscope calculates per-contributor productivity metrics. If a team member has been contributing commits but isn’t appearing in your team’s per-contributor metrics, that means Macroscope cannot attribute their commits to a GitHub identity.
If a contributor doesn’t appear in per-contributor metrics:
  • Check that they’ve verified their email address in their GitHub settings
  • Check that their commit author email matches a verified email address on their GitHub account
  • To ensure proper attribution:
    • Contributors should configure their local Git to use the same email address that’s verified on their GitHub account
    • Use git config --global user.email "verified-email@company.com" to set the correct email

​
Managing External Contributors

You can control whether external contributors (e.g. open-source contributors) are included in your Project Summaries and/or in your Productivity Metrics in Settings under External Contributors. These are two separate settings because the value of external contributions differs by circumstance.
For example, you may want to include external contributors in Project Summaries to capture the full history of an open-source project, but exclude external contributors from Productivity Metrics (e.g. Clickity Clack, Top Contributors) so those metrics reflect only your employees’ work.