Purpose

Biggest commits shows the top of biggest commits in a project code base by connected GIT repository.

How metric helps

Metric helps to look after the commits size to identify exceptionally biggest, understand tendency and probably reduce the size. Per industry best practices: the smaller commits the better. Big commits create an unnecessary overhead for development teams due to a more expensive code reviews and more expensive troubleshooting if anything got broken after that commit.

How it works

Chart overview

Chart shows Biggest commits in a number of lines - Axis X by a team member - Axis Y. Chart can be viewed for the last 7/30/90 days. When hover over a series hint appears:

• Date/time - the last commit date & time
• Committer name - name of a person made the commit
• Commit size  - number of lines a commit contains along with a number of deleted and added lines
• Commit comment - the latest commit comment left by the committer
• Commit hash - a unique identifier of a commit given by Git

Next to the chart name there is a link to GIT repository ('arrow').

Calculation formula

A commit size is a count of all modified code lines within it.

RAG thresholds: n/a.

Data Source

Data for the metric can be collected from GIT.