Merge readiness
Last updated .
What is the merge readiness score?
Merge readiness is a score from 1 to 5 on every MergeSafe review, set by the most severe verified findings: 5/5 means nothing was found, any verified P0 scores 1/5, and 4.5/5 or above counts as merge ready.
| Score | When | Shown in the app as |
|---|---|---|
| 5/5 | No verified findings. | Merge ready |
| 4.5/5 | No P0 or P1, at most two P2s, and at least one P2 or P3. | Merge ready |
| 4/5 | No P0 or P1, more than two P2s. | Nearly ready |
| 3/5 | Exactly one verified P1. | Needs work |
| 2/5 | Two or more verified P1s. | Not ready |
| 1/5 | Any verified P0. | Not ready |
Rules that adjust it
- Unverified blockers cap it at 3/5. A P0 or P1 that could not be verified holds the score at 3/5 at most, but never drops it to 1 or 2.
- Partial coverage caps it at 4/5. If a review could not cover the whole diff, the score is at most 4/5 and the summary says so.
- Unverified P2 and P3 findings don’t count. They are listed, not scored.
- Replies move it. When a disputed finding is withdrawn or downgraded, the score is recalculated at no charge.
Where you see it
- At the top of each summary comment, for example MergeSafe · 4.5/5 · 1 P2, with a one-line reason.
- In the review history table in the pull request description, one row per reviewed commit.
- On the Pull requests page in the app, where you can filter by it.
Related: Severity and the glossary entry merge readiness.
Next: Replying to a finding →