Review quality metrics

These metrics reflects quality of review performed by developer with PRs of other developers.

Required reviews count

Some pull requests may have a list of developers who were required to conduct a review. This metric just shows amount of such PRs for each developer.

Comments count

This metric shows the number of comments that developer leaves in the PRs of other developers. Higher value is better and means that developer more thoroughly reviews the code (or maybe code quality of PRs are low).

Conventional comments count

This metric shows the number of comments match standard for formatting comments, it's always good to have good formatted useful comments so higher value is better and means that developer more often makes great comments.

Reviews count

This metric shows the number of approved PRs by developer. Higher value is better and means that developer more often approves pull requests.

Bad reviews count

This metric shows the number of rejected/declined PRs by developer. Lower value is better and means that developer more often makes good reviews.

Review involving

This metric shows ratio of number of pull requests where developer leaves at least 1 comment or approves it to total number of PRs. Higher value is better and means that developer participates in more reviews of PRs (ideal result is 100%).

Average review time

This metric shows average time that developer spends on review (time between creating and approving PR). Lower value is better.

Reviewed LOC and average reviewed LOC

This metric shows lines of code (LOC) reviewed by developer. Higher value is better and means that developer participates in reviewing bigger PRs.

Code quality metrics

These metrics reflects code quality of developer's pull requests.

Open pull requests

This metric shows the number of PRs opened by developer.

Time since last open pull request

This metric shows the time since developer opened last pull request.

Average merge time

This metric shows average time that developer spends on merging PRs (time between creating and merging). Lower value is better and means that developer closes tasks very quickly and more code are delivered to production.

Average PR comments

This metric shows average amount of comments that developer receives in his PRs. Lower value is better and means that PRs have good quality of code.

Changed LOC and average changed LOC

This metric shows lines of code changed by developer in his PRs.