Change Request Commits

Question: How many code change commits are included in a change request?

Synonyms: Pull Request Commits, Merge Request Commits


This metric enumerates each code change commit associated by a git platform with a change request, and lists the contributors who made each commit, and any references to parent commits embedded within it.

There are a number of nuances to be aware of when reviewing the change request commits reported by a platform. If, when, and how commits are squashed has a significant influence on change request commit data reported when compared to code change commit data mined from a software repository directly. It is, for example, common to squash commits when a change request is merged. Often this leads to there being less detail in the change request commits data provided by an API. In addition, each change request also becomes a commit in the branch to which it was merged git log. Notably, only commits that make it to the default branch are reflected in a repository’s code change commits metric, mined from the git log. It is possible to mine commits and pull request commits from other branches, but this practice is not common.

NOTE: There are often Change Requests that are not into the default branch.

Caution for 2021: Analysis of change request commits against the main branch should take into account recent changes in the name of the primary branch, which many projects changed from “master” to “main” from 2021 forward. A small number of projects use names other than main or master for their default branch, and tools should take this into account by always checking the name of the default branch before analyzing the commit log. This is especially the case when the name of the default branch changes.


  1. This metric provides information that can help inform how, in general, a repository’s change request process is managed. The count of commits in a merge request and the number of people involved in those commits tend to be locally consistent, but across all of open source, there is a wide range of patterns.
  2. Enable a maintainer to know which contributors have a history of collaborating with others on a single change request.
  3. Larger commit totals on a change request signal greater complexity for merging. Being aware of this helps to identify potential contributors for future maintainer status (i.e. required skill level).,
  4. Knowing the number of change request commits creates awareness of potential change request’s complexity and could influence repository policies and guidelines.
  5. To identify change requests that are anomalous to more typical commit patterns (i.e., commit size, commit sequence), or change request patterns (i.e. number of commits).
  6. This metric may inform the diversity and inclusiveness of a project through exploration of the demographics of contributors who get commits accepted through a change request process.


The usage and dissemination of health metrics may lead to privacy violations. Organizations may be exposed to risks. These risks may flow from compliance with the GDPR in the EU, with state law in the US, or with other laws. There may also be contractual risks flowing from terms of service for data providers such as GitHub and GitLab. The usage of metrics must be examined for risk and potential data ethics problems. Please see CHAOSS Data Ethics document for additional guidance.


  • Lines of code added per commit
  • Lines of code removed per commit
  • Change in code over the period of time
  • Iteration in the commits (How many times is the same file touched in the commits included in a merge request)
  • Number of files changed per commit
  • Contributors per commit



Source: Image is obtained from Augur API

Tools Providing the Metric

Data Collection Strategies

  • Mining git logs
  • API Calls to Platforms



  • Vinod Ahuja
  • Kevin Lumbard
  • Elizabeth Barron
  • Sean Goggins
  • Armstrong Foundjem

This metric was last reviewed on February 22, 2022 as part of the 2022-04 release.