| --- |
| title: "PR Deploy Time" |
| description: > |
| PR Deploy Time |
| sidebar_position: 2 |
| --- |
| |
| ## What is this metric? |
| The time it takes from when a PR is merged to when it is deployed. |
| |
| ## Why is it important? |
| 1. Based on historical data, establish a baseline of the delivery capacity of a single iteration to improve the organization and planning of R&D resources. |
| 2. Evaluate whether the delivery capacity matches the business phase and demand scale. Identify key bottlenecks and reasonably allocate resources. |
| |
| ## Which dashboard(s) does it exist in? |
| |
| |
| ## How is it calculated? |
| You can define `deployment` based on your actual practice. For a full list of `deployment`'s definitions that DevLake support, please refer to [Deployment Frequency](/docs/Metrics/DeploymentFrequency.md). |
| |
| <b>Data Sources Required</b> |
| |
| This metric relies on PR/MRs collected from GitHub or GitLab. |
| |
| <b>Transformation Rules Required</b> |
| |
| N/A |
| |
| ## How to improve? |
| |
