Developer File Change Patterns Bubble Graph

Understanding commit behavior can inform resilient teams.

Who is making foundational contributions? Do developers spend an even balance of time working on others or their own code? The new Developer File Change Patterns bubble graph **can show you all this and more.

Let's look at the underlying data;


Metric
Description

Number of Files Created

# Files Created		Count of all files created. Each file is created exactly once. Files can be deleted and are no longer part of the current repository, but did exist previously.

Number Own Files Changed

# Own Files Changed		Count of all file changes made to files created by that contributor.

Number of Others' Files Changed

# Others' Files Changed		Count of all file changes made to files created by another contributor.


These numbers get combined and divided in a few different ways in the Types of Changes by Committer Name table beneath the bubble graph. They can be downloaded with the CSV icon.


Data Points

Contribution is about more than just quantity of commits. We use ratios to make a clearer comparison across the entire team.

The Expertise Bubble Graph has three data points;

  • Bubble Size - proportionate to number of commits. Each bubble is a contributor.
  • Y-axis - Ratio showing a developers Number of changes to others' files : (to) 1 file created
  • X-axis - Ratio showing a developers Number of changes to own' files : (to) 1 change to others' files

Point plotted along the axis indicate the user hasn't changed their own files, created files, OR changed others' files, therefore no ratio can be calculated.


Sidebar

When the page loads the sidebar shows details about activity across the repository.

Clicking on a bubble brings up details about the contributor.

To see the repository details again you can close and reopen the sidebar using the icon, or refresh the page.


Making Sense

As developers more further to the right, they spend more time making changes to the code they created than they do creating files.

The higher up on the y-axis a developer is, the more time they spend making changes to others code.