Purpose

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

How metric helps

Biggest commits helps to look after the commits size to identify exceptionally biggest ones, understand tendency and probably reduce their 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 metric works

Chart overview

Chart shows Top 20 biggest commits in a selected code repository. Chart can be viewed for the last 7/30/90 days. Names of team members are at Y-axis, size of commits (in a number of  code lines) - X-axis. When hover over a series - a hint appears with the following information available:

• Date/time - the last commit date & time

• Committer name - name of a person who made the commit

• Commit size  - number of lines a commit contains along with a number of deleted and added lines

• Commit comment - the comment left by the author for this commit

• Commit hash - a unique identifier of a commit given by Git

Next to the chart name there is a link to navigate to the GIT repository ('arrow' icon) for further details.

Open

Calculation 

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

If the setting 'Include merge requests into statistics' is selected in GIT configuration the metric values might increase.

RAG thresholds: n/a.

Data Source

Data for the metric can be collected from GIT.