Lines of Code
This topic provides a guide on how the Lines of Code metric is calculated on SEI.
The Lines of Code metric is a crucial indicator of developer productivity and codebase evolution over time.
This metric is pivotal in measuring a developer's contribution, quantified by the total lines of code added, deleted, or changed in the selected time period.
According to industry standards, an ideal range for the LOC metric for a software engineer is between 125 and 185 lines of code per month. However, note that this range may vary depending on factors such as project complexity and coding conventions.
Scope of Measurement across different reports
The Lines of Code metric is measured across two types of reports on SEI: Trellis Reports and SCM Reports.
Trellis Reports
In Trellis Reports, the Lines of Code metric calculates the Total Number of Lines of Code contributed by an engineer within the selected time frame. The calculation includes the Cumulative Sum of Lines of Code Added and Lines of Code Changed by the respective engineer across commits.
The metric value in the Trellis report is normalized to show the Average Number of Lines of Code contributed Per Month. This gives a comprehensive view of the volume of work a developer contributes to a project each month.
In the Raw Stats report, the metric displays the Total Number of Lines of Code contributed by the engineer within the selected time frame.
SCM Reports
The Lines of Code metric in SCM reports provides a more granular representation of a developer's contribution. The metric measures the total lines of code that are included in Pull Requests (For SCM PRs Report) and Commits (For SCM Commits Reports). This includes:
Lines of Code Added: It measures the new lines of code a developer adds for an associated pull request or commit in the respective report (i.e., SCM Commit Report and SCM PRs Report).
Lines of Code Deleted: It measures the lines of code a developer deletes for an associated pull request.
Total Lines or Lines of Code Modified or Changed: It measures the total lines of code changed as a result of the addition or deletion of lines for an associated pull request or commit in the respective report.
Scope of Measurement across different platforms
SEI measures the Total Number of Lines of Code that are included in Pull Requests (PRs) across various SCM tools such as GitHub, Bitbucket, GitLab, and Azure Repos. The calculation process varies depending on the tool used.
GitHub, Bitbucket and GitLab
Merged Pull Requests (PRs): SEI calculates the Lines of Code metric for merged PRs using the
merge SHA (Commit ID). This approach ensures accuracy by considering the Final State of the codebase after merging, which includes the cumulative data of all code modifications. This consists of Total Lines Added, Deleted, and Files Changed as part of the merge commit.PRs in
OPENorCLOSEDStates: Lines of Code metric for open and closed PRs are determined via the respective SCM tool's API. This includes the Total Count of Lines Added, and Deleted, and the Number of Files modified in all the commits that make up the PR.
When using the Rebase and Merge strategy, the latest commit in the PR is recognized as the merge commit. This leads to incorrect calculations for the Lines of Code metric, as rebasing rewrites the commit history, which does not accurately reflect the actual changes made in the original commits and thus changes the count of lines added, deleted, or modified.
SCM PRs reports: Here the values for Lines Added, Lines Deleted, and Files Changed correspond to the lines of code added, deleted, and the respective files changed for the associated Pull Request. The Lines Changed field is calculated as the number of lines changed or modified, which is the summation of lines added and lines deleted as part of the associated pull request.
SCM Commits reports: Here the values for Lines Added represent the lines of code added as part of the associated Commit. The Total Lines field is calculated as the total number of lines changed, which is the summation of lines added and lines deleted as part of the associated commit.
For SCM reports, the values for lines of code added and deleted are the same as those received from the SCM tool for the associated Pull Request or Commit. These values are not calculated by SEI.
To receive the file's changed data, make sure you have set the
fetch_commit_fileskey in your integration configuration toYes. This will enable SEI to retrieve the necessary data from the SCM tool.For BitBucket Cloud and Server to receive the data for Lines added and Lines deleted for the associated pull request or commit make sure you have set the
fetch_commit_fileskey in your integration configuration toYes. This will enable SEI to retrieve the necessary data from the SCM tool.
Azure DevOps
There are currently some known issues with all SCM reports for the Azure DevOps integrations. As a result, the data for SCM metrics such as Lines of Code and Files Changed may be displayed as either zero or incorrect. This issue will be fixed in future releases.
Commits encompassing more than 256 files are automatically excluded from the calculation.
Calculation Example
Let's consider a scenario with multiple PRs and commits:
Developer A worked on 3 PRs last month on GitHub
PR #1 (Merged): This PR had two commits, with the merge commit resulting in 100 lines added and 50 lines deleted. Therefore, the total number of lines of code changed was 150.
PR #2 (Open): It consisted of four commits, adding a total of 150 lines and deleting 75. The total lines of code changed amounted to 225 lines.
PR #3 (Closed): This included one commit with 20 lines added and 10 deleted, making the total lines of code changed to 30 lines.
PR #1
Merged
Merge Commit
+100
-50
150
PR #2
Open
Commit #1
+30
-10
40
PR #2
Open
Commit #2
+25
0
25
PR #2
Open
Commit #3
+15
-5
20
PR #2
Open
Commit #4
+80
-60
140
PR #3
Closed
Commit #1
+20
-10
30
For SCM reports, the values for lines of code added and deleted are the same as those received from the SCM tool for the associated Pull Request or Commit. These values are not calculated by SEI.
The calculations for Developer A in the SCM reports are:
SCM PR Reports
PR #1
100
50
150
4
PR #2
150
75
225
6
PR #3
20
10
30
3
SCM Commits Reports
Commit #1 (PR #1)
100
50
150
4
Commit #1 (PR #2)
30
10
40
2
Commit #2 (PR #2)
25
0
25
1
Commit #3 (PR #2)
15
5
20
1
Commit #4 (PR #2)
80
60
140
5
Commit #1 (PR #3)
15
5
20
2
Last updated