Accessing the Report
Navigate to More Reports > Deep Work from the left sidebar.
Filters
Filter | Options |
Date range | Preset ranges (Last 3 Months, etc.) or custom dates |
Team selector | All Teams (with count), or specific teams |
Apply Filter | Additional filters (repositories, members) |
Save Filters | Save your current filter combination |
A "Showing all Repositories" badge appears when no repo filter is applied.
Activity Heatmap
The main visualization is a heatmap grid where:
Rows = hours of the day (00:00 through 23:00)
Columns = days of the week (Monday through Sunday)
Cell color = activity volume for that hour/day combination
The description reads: "Sum of GitHub activities (commit, comment, push, etc.)."
Color Intensity
Color | Meaning |
Dark blue | High activity — many GitHub events in that time slot |
Medium blue | Moderate activity |
Light blue | Low activity |
White/empty | No recorded activity |
Timezone Selector
The heatmap defaults to your account's timezone setting. A dropdown in the top-right corner of the heatmap (e.g., Asia/Manila) lets you switch to a different timezone without changing your account settings — useful for seeing when a distributed team is active in their local time.
Associated Activities
Below the heatmap is an Associated Activities section. Click on any cell in the heatmap to see the specific activities (commits, comments, pushes) that occurred during that hour/day slot.
Before clicking, the section shows: "Click on the graph to see associated activities."
Reading the Heatmap
Peak coding hours
Look for the darkest cells — these are the hours when your team is most active.
After-hours and weekend work
Activity in late evening rows (21:00–23:00) or Saturday/Sunday columns may indicate:
On-call work or incident response
Deadline pressure
Team members in different time zones
Meeting gaps
A consistent white/light band during working hours (e.g., 12:00–14:00 every day) likely corresponds to lunch or recurring meetings.
Use Cases
Scenario | How the Heatmap Helps |
Planning “no meeting” blocks | Identify when developers are already most focused and protect those windows |
Detecting burnout risk | Consistent after-hours or weekend activity may signal overwork |
Optimizing standup times | Schedule standups outside of peak coding hours |
Understanding distributed teams | Switch the timezone to see when each region is active |
FAQ
Q: What activities are included in the heatmap? A: All GitHub activities — commits, comments, pushes, PR actions, etc. It is not limited to just commits or PRs.
Q: Does the heatmap include bot activity? A: No. Bot accounts are automatically excluded.
Q: Can I change the timezone? A: Yes. It defaults to your account timezone, but you can use the dropdown in the top-right corner to view activity in any timezone without changing your account settings.
Q: Does this work with GitLab or Bitbucket? A: The description references GitHub activities specifically. Check with [email protected] for GitLab/Bitbucket coverage.
Q: Who can access this report? A: Both Admin and Member roles. The data shown depends on the team filter selected.