The GitHub Analytics Tool retrieves data from your GitHub repository and uses it to provide you with insights into your software development team's performance using commonly used software development metrics. It assesses your team based on weekly issue completion, PR completion, cycle time, and open vs. closed issues. It compares your team's scores to the top 100 most starred, forked, and active GitHub repositories.
The GitHub Analytics Tool fetches your team’s data from GitHub and compares that data to the top 100 GitHub repositories. For public repositories, the data available is public, so all that is required to input is the repository URL. For private repositories, you will need to sign into GitHub for us to retrieve that information.
Our current top 100 repositories are listed below:
The GitHub Analytics Tool determines the top 100 GitHub repositories by:
The GitHub Analytics Tool calculates the following metrics:
We would like to acknowledge Goodharts Law and conceed that the metrics above can be gamed to improve the metric score without actually making your team more productive.
The GitHub Analytics tool calculates a set of metrics based on recent GitHub issues and pull requests. Those metrics are scored between 30 - 100 and then combined to create an overall grade based on the following metric weights.
|Issue completion (weekly)||25%|
|PR throughput (weekly)||25%|
|Issue cycle time||25%|
|Code review time||25%|
Your grade is compared to the top 100 GitHub repositories. Your score is the percentile your team has achieved compared to these repos (e.g., 75th percentile means that your score is better than 75% of the top 100 GitHub repos).
Yes, you can use the GitHub Analytics Tool to assess personal projects, so long as there is a repository, public or private, associated with the project.
Once you have your results, it’s time to do some evaluation. If your results were not what you were hoping for, it might be time to reconsider some of the processes currently blocking your team. Are you spending too much time on the wrong tasks or updating issues? Are too many meetings preventing your team from having time for focused work? We recommend using a tool like Zenhub to continue gaining insights into your team’s most common blockers, how their work flows through pipelines, and what their capacity looks like.
The GitHub analytics tool only uses GitHub metadata on the repository, issues, and pull requests. This includes:
No, the GitHub Analytics Tool does not read, store, or persist your source code.
Zenhub is not affiliated with GitHub or any companies mentioned as users of our product.
All other trademarks and copyrights are property of their respective owners. © Zenhub 2023