# Release Merge Frequency

### **Release Merge Frequency**

<div data-with-frame="true"><figure><img src="/files/W3bx1IbwxUk4m1EVDUZL" alt=""><figcaption></figcaption></figure></div>

#### Formula =

```
(Total number of PRs merged to master or main in that selected time period) / 
(Total number of days in the time period)
```

* Release Merge frequency measures how often code is merged to the main/master branch. Elite Release Merge Frequency represents a stable and healthy delivery.
* This metric would help you understand the number of PRs being pushed to production in a given time. This can work independently of your sprint cycle time. You can learn more about them [<mark style="color:purple;">here</mark>](https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance).
* Too low Release Merge frequency indicates that there may be bottlenecks in review, or requirements, and teams are delivering features at a slower pace.
* High Release Merge frequency shows that your team can quickly provide value and react to feedback or changes.

#### Industry Benchmarking

<div data-with-frame="true"><figure><img src="/files/cT3xhKxBJpFYGhI9Xtss" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hivel.ai/metrics-and-definitions/speed/release-merge-frequency.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.