# Merge Time

The "Merge" stage represents the average time taken from the approval of the Pull Request to its integration into the main codebase.

For all the merged PRs, Typo calculates the average time between the approval of the Pull Requests and the time they are merged to the main/master/production branch. The final merge branch to be considered is configurable & can be set as per your processes. In case a Pull Request is merged without review approval, the Merge Time will be calculated from the first review comment on that Pull Request. In case a merged Pull Request does not have any review comments and approval, the Merge Time will be calculated from the time that Pull Request was raised for review.

<div align="left"><figure><img src="/files/srBzDsv9HITHdH79zl1H" alt="" width="375"><figcaption></figcaption></figure></div>

> Benchmarking merge time helps teams establish performance standards and compare their merge time metrics against industry benchmarks or internal targets, facilitating continuous improvement and identifying areas for optimization in the development workflow.

### **How does measuring merge time help in improving the Engineering team's efficiency?**

1. **Identifying Bottlenecks:** Tracking merge time helps pinpoint bottlenecks in the development process, whether it's due to code complexity, review backlog, or other factors, allowing teams to address them promptly.
2. **Improving Collaboration:** By measuring merge time, teams can assess how efficiently they collaborate on code changes. Longer merge times may indicate communication gaps or a lack of coordination among team members, prompting collaboration improvements.
3. **Optimising Workflows:** Analysing merge time data enables teams to evaluate the effectiveness of their workflow and identify areas for optimization. This might involve streamlining code review processes, implementing automation, or revising branching strategies.
4. **Enhancing Productivity:** Shorter merge times typically correlate with higher productivity and faster delivery of features or bug fixes. By setting benchmarks and tracking progress, teams can strive for continuous improvement and higher efficiency in their development cycles.


---

# 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://typo.gitbook.io/typo-help-docs/engineering-metrics/pull-request-metrics/merge-time.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.