GitHub Insights

Track your team's development performance and get actionable recommendations for improvement.

GitHub Insights in Zenhub provides a productivity dashboard that analyzes your team's GitHub activities across 6 key metrics. The dashboard combines performance scoring with personalized recommendations to help you improve code review processes, planning efficiency, and overall development productivity.

Accessing the report

Navigate to Reports in the left sidebar and select GitHub Insights. The dashboard automatically loads data from all repositories connected to your current workspace. Use the date range controls to focus your analysis on specific periods — the dashboard requires repositories with closed issues and merged pull requests during the selected timeframe to generate meaningful metrics.

Understanding your productivity score

Your productivity score appears as a percentile ranking comparing your team's performance against top GitHub repositories. Each of the 6 metrics receives a score between 30 and 100 points, combined with equal 25% weighting to create your overall grade. A 75th percentile score means your team performs better than 75% of these high-performing repositories.

Use your score as a baseline for tracking improvement over time rather than an absolute measure of team success. If your score shows as null, your connected repositories don't have enough closed issues or merged pull requests in the selected time period to generate meaningful calculations.

The 6 productivity metrics

Issue completion is the total number of issues your team completed within the selected period.

Issue lead time is the average number of days issues take to move from created to closed. Shorter lead times indicate efficient issue resolution.

Issue completion ratio is the ratio of issues closed to issues opened. A ratio above 1.0 means your team is resolving issues faster than new ones are being created.

PR throughput is the number of pull requests merged within the period, showing your team's code delivery pace.

Code review time is the average number of days from when reviews start until they are completed.

PR merge ratio is the ratio of pull requests merged to pull requests opened and abandoned. Higher ratios indicate fewer wasted efforts.

Interpreting productivity patterns

Strong teams typically show consistent performance across all 6 metrics rather than excelling in some areas while struggling in others. Long lead times or review times combined with lower completion ratios often indicate process bottlenecks worth addressing. Track metrics over different time periods to identify improving or declining productivity patterns and the impact of process changes.

Using recommendations

GitHub Insights provides recommendations in 2 categories. Issue hygiene recommendations cover prioritization strategies, assignee allocation, and regular cleanup practices. PR hygiene recommendations focus on associating pull requests with issues, timely reviews, and workflow optimizations. Focus on recommendations that address your lowest-performing metrics first.

FAQ

Q: Why is my productivity score showing as null?
A: This indicates your connected repositories don't have enough closed issues or merged pull requests during the selected time period. Connect repositories with recent activity or adjust your time period to include more development activity.

Q: How often should I check GitHub Insights?
A: Review productivity metrics monthly or quarterly to identify trends without over-optimizing for short-term fluctuations. Use insights during sprint retrospectives and team planning sessions for systematic improvement.

Q: Which productivity metrics should I prioritize for improvement?
A: Start with your lowest-scoring metrics and focus on recommendations that address workflow bottlenecks. Issue and PR lead times often provide the biggest impact when improved, as they affect multiple other metrics.

Q: How do I know if my productivity improvements are working?
A: Track your score and individual metrics over time. Meaningful improvements typically show consistent positive trends over 2–3 months rather than immediate score increases.

Q: Do GitHub Insights work for teams that don't use traditional issue tracking?
A: The insights require GitHub issues and pull requests for meaningful calculations. Teams using external issue tracking may see limited value unless they also maintain GitHub issues for development workflow tracking.