What this section is for
Open a profile to see commits, pull requests, reviews and technologies. Main metrics use the selected dates and repository. The growth chart separately covers 12 months across the team; the current unfinished month is excluded from comparisons. Git activity is not working time, and calculated grades and indices do not establish individual skill.
When to use
- Before a one-to-one, to prepare questions about specific tasks and changes.
- During onboarding, to look at a new developer’s first commits and reviews.
- When someone reports a large review workload and you want to discuss how the work is shared.
Quick start
- 1Search by name or email and choose the date range and repository.
- 2Open the profile and inspect commits, pull requests and reviews for the selected dates.
- 3Read the heuristic warning before using grades, badges or indexes.
- 4Use the growth chart to compare months. Its dates and repositories are separate from the main metric filters.
Key settings
| Setting | What it does | How to use it | Common mistake |
|---|---|---|---|
| Developer seat | Controls which profiles are unlocked; metrics stay hidden without an active seat. | For the demo, choose a developer whose work you know and compare the metrics with their actual tasks. | Interpreting a locked profile as missing data: viewing it requires an active demo or paid seat. |
| Period | Sets dates for the main activity metrics. The growth chart uses a separate 12-month period. | Account for leave, task changes and release freezes when choosing dates to compare. | Reading a two-week window during a release freeze and concluding someone has slowed down. |
Usage example
Scenario: An engineer says most of their time goes into reviewing other people’s work.
- 1Open their profile and compare Reviews Given against Reviews Received and against the team’s numbers.
- 2Check average review time and the number of collaborators. Ask which reviews require the most effort.
- 3Discuss which reviews other people could take on. Check the metrics again after changing the allocation.
What this shows: You have specific reviews to discuss when looking at workload. Their count adds to the developer’s account but does not measure all their effort.
FAQ
Does code level measure productivity or seniority?
No. Grades, indices and confidence values use fixed rules applied to available data. Their accuracy as skill assessments has not been established. They miss work such as design, mentoring and discussions.
Why does it say insufficient data?
Available activity has not reached the threshold configured for that metric. Crossing the threshold allows a calculation to appear; it does not establish the accuracy of the assessment.
Can I compare two developers directly?
Direct numerical comparisons without context mislead: roles, tasks, repositories and work outside Git differ. Use profiles to ask questions about work and process, rather than rank people.
Tips
- Discuss noticeable changes with the developer. Fewer commits may reflect different tasks, help given to colleagues or time off.
- Share profile data according to access permissions and your organisation’s rules for people analytics.