See what's new on Keypup!  📢

Change Failure Rate (Commits based)

Connect your Git repository to calculate the ratio of fix-related commits among all merged pull requests commits.

Use CFR Metric

Automate Change Failure Rate (CFR) Calculation from Your Git Pull Request Commits

with the

Change Failure Rate (Commits based)

Connect your Git repository to calculate the ratio of fix-related commits among all merged pull requests commits.

Use CFR Metric
Change Failure Rate (Commits based)Change Failure Rate (Commits based)Change Failure Rate (Commits based)

From startups to large enterprises, Keypup serves all the unique complexities related to project size, structure and teams, including:

Understand the Commits-Based Change Failure Rate

The commits-based CFR detects commits related to bug fixes using keyword search. The template identifies commits containing the keyword "fix" among all merged pull requests and calculates its ratio. You should amend the keyword (or list of keywords) to reflect your own naming convention.

What Is a Good Change Failure Rate?

A team or organization with a CFR between 0% and 15% is considered to be an elite performer based on DORA metrics. Medium performers observe a CFR rate from 15% to 45%, while low performers observe above a 45% rate.

How to Reduce Your Change Failure Rate

To keep your CFR between 0 and 15%, you should apply industry best practices such as:

  • Adding linters and code analysis tools so developers can review their styling issues.
  • Automating end-to-end testing (E2E).
  • Documenting test edge cases, unstable flow, and incidents.
  • Ensuring your test environment(s) reflects your production.
Use CFR Metric