@mutmutco/pi-plugin 4.3.65 → 4.3.66
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -128,7 +128,13 @@ Run it again after Step 7. A repo is not ready for real developers until every c
|
|
|
128
128
|
names an explicitly manual-only item that the master has accepted for that repo. For a deployable repo the
|
|
129
129
|
report ends with the train doctor verdict per lane (`release`; plus `rcand` on a full track) — the same
|
|
130
130
|
`mmi-cli devops train doctor` door `/release` and `/rcand` open (#6070); a `ready: false` there is an
|
|
131
|
-
unfinished repo
|
|
131
|
+
unfinished repo, **with one expected exception**: a full track's two lanes start from different branches
|
|
132
|
+
(`release` from `rc`, `rcand` from `development`) and one checkout stands on one branch, so the lane you
|
|
133
|
+
are not standing on reports the never-healed `branch-mismatch` blocker (#6432). Verify is read-only and
|
|
134
|
+
does not check the other branch out: a lane whose ONLY finding is that mismatch is printed `NOT EVALUATED
|
|
135
|
+
from this branch` and does not fail the verify (#6677). That is the finished state, not a gap — run
|
|
136
|
+
`mmi-cli devops train doctor --lane <lane> --json` from that lane's own branch for its verdict. Any other
|
|
137
|
+
blocker in that lane, or an unread origin, still makes the report red.
|
|
132
138
|
|
|
133
139
|
**Two verify FAILs are un-run apply steps or API lag, not code bugs — diagnose them as such, but never as
|
|
134
140
|
acceptable end states (#2928):**
|