What does "NOT READY" actually mean, and how do I get to "READY"? #3
-
|
The big badge on the Overview says NOT READY next to the score ring. Is that a separate check from the score, and what gets me to READY? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
They're one signal, not two. READY / NOT READY is derived directly from the Production Ready Score — there's no separate test. NOT READY simply means the score is below the production-ready threshold; READY means it's at or above it. The threshold is the same for every Hub workspace in this release (not configurable per tier). Open the lowest-scoring area first — fixes there move the overall weighted score the most. One thing that trips people up: your score can move even when you didn't touch your code — if a release adds a new rule your code triggers, or retires one, the area denominators change. The Coverage tab shows which rules actually ran. |
Beta Was this translation helpful? Give feedback.
They're one signal, not two. READY / NOT READY is derived directly from the Production Ready Score — there's no separate test. NOT READY simply means the score is below the production-ready threshold; READY means it's at or above it. The threshold is the same for every Hub workspace in this release (not configurable per tier).
To move from NOT READY to READY:
Open the lowest-scoring area first — fixes there move the overall weighted score the most.
Within that area, fix HIGH before MEDIUM before LOW. A HIGH fix moves a rule 0 → 100; a LOW fix only 75 → 100. Bigger lever, more score recovered.
Re-run the scan. The label flips to READY the moment the score crosses the threshold.
One thing t…