GitClear calculates more than 30 different pull request metrics designed to lead a team toward actionable opportunities to improve communication and accelerate release velocity.
If you'd like to skip straight to learning about our sections, they are:
Here are 10 questions that GitClear's PR stats can contribute data to help answer:
During what phases of the pull request process is the lion's share of your developer's work taking place?
Before the pull request is submitted for review. Perfect 👌. Only the committer themselves needed to spend time on the work that occurred in this phase.
After the pull request is submitted for review. Expected, in moderation. A good litmus: if the total Line Impact accumulated during PR is less than what was accumulated before the PR was submitted, you are probably OK. If more work happens after review than before the PR was submitted, that implies that the committer was lacking instruction/documentation or clarity necessary to perform their duties independently.
After the pull request is merged. Bad news. Implies that the QA and review process did not complete all work that was necessary for the pull request to be deployed without defects to production. 🐛
Who on the team has been the most prolific PR commenter? What are the downstream implications of these comments -- that is, do those who receive suggestions from this individual tend to act upon them?
Which PRs have been opened the longest, and what is holding the team back from getting them closed?
Are submitted PRs at or below the manager's target size? How is that trending over time?
Are submitted PRs at or below the manager's target maximum comments left per PR? How is that trending over time?
How is the Cycle Time for pull requests changing as time passes? (A potential indicator of tech debt when it's increasing)
Are pull requests being merged without review? How often does that happen and what ensues after?
Is the team moving in generally a positive direction of having less pull requests opened for less total days?
Are there any assigned reviewers who have been especially tardy in offering their review?
What are the themes of the feedback that are received (e.g., "this could be a performance concern," "please follow the styleguide," etc) on a per-committer basis?
If you have struggled with questions like the above and would like to connect with a for-hire CTO who has experienced in answering these questions using GitClear, drop a line to email@example.com and we have referrals for highly rated Engineering Execs who can help you dig into the finer details in answer the above. GitClear does provide reports that can be used to answer these questions without a professional, but it takes some time to fully learn what stats are available, and how your team's values compare to industry benchmarks.
GitClear's Pull Request Stats are divided between four tabs:
High-level stats that show the bigger picture of what's happening across your repos or in a team:
Some of the stats available among Activity Stats
Read more about Activity Stats here: Classic Pull Request stats: how to optimize what matters for long-term health
Granular list of pull requests that are underway (or were underway during the time range you might select):
View pull requests that are lingering (no recent work over last five days), and that are more actively on the way to being merged
Read more about Open PR stats here: Kick-start lingering pull requests
Granular list of pull requests that were recently completed:
Reassuring to see a team completing pull requests below the size targets (indicated by the green chark marks)
Read more about closed PR stats here: Learning from PR overruns during your retrospective meeting
What are the patterns in how teammates interact? Focus on an entire team, repo, or an individual.
Compare stats for the current period vs. previous periods to get a sense for which direction the team is trending
Read more about Collaboration Stats in PR collaboration hygiene: are things getting better or worse? Is collaboration slowing velocity?
Read about that at Kick-start lingering pull requests#Exiling Pull Requests