Developer | PR Size

Definition (Hover Text)

Pull Request (PR) Size measures the number of source lines of code (SLOC) affected by a pull request.

Source Tools

Github, Gitlab, Bitbucket, Azure Repo

Graph type

Line

X Axis - Days/Weeks/Months
Y Axis - Count (Lines of Code)

Filters

Branches & Developers

Hover Format on KPI

<From Date - To Date>: Lines
No. of PRs: XX

Fields on Explore

• Project

• Repository

• Branch

• Days/Weeks

• Developer

• No. of Merge Requests

• PR Size (Lines of Code)

Business Logic

Calculation Formula

Physical SLOC (Source Lines of Code):

• Option 1: Counts all lines in the program's source code, including comments and empty lines. This approach is preferable in the first phase.

• Option 2: Counts only the lines in the source code, excluding comment lines, blank lines, or lines containing only white space.

Logical SLOC (LLOC): Measures the number of executable statements in the source code.

Source:

• Wikipedia - Source Lines of Code

• SmartBear Blog - Should Code Review Metrics be LOCs or SLOCs

Trend

A decreasing trend is considered positive

Maturity Levels

M1: 0-2
M2: 2-4
M3: 4-8
M4: 8-16
M5: >16

Instance level thresholds

4

Configurations

Processor Fields

Nil

KPI Specific fields

Target KPI Value

How to Validate KPI

Suggested ways of working

• Ensure each pull request follows standard formatting to allow proper analysis of size.

Sample JQLs

N/A

Benefits of KPI

How does the KPI help

The PR Size KPI helps by indicating the complexity and scope of changes in a pull request. It aids in managing review workload, as smaller PRs are easier to review, and larger ones may require more attention, reducing review delays and improving code quality.