Repository navigation
test(bundle): drive loadTide's configured tide.labels arm (tide.ts:542) through dist/index.js - #473
Conversation
|
Important Held for human review by the hive's ACMM level gate. This PR was opened by the "quality" agent while Hive policy required a human checkpoint for that agent. Non-outreach agents are held at ACMM L3–L5; the Hive will keep the |
|
Please add a kind label with |
jeefy
left a comment
There was a problem hiding this comment.
All four cases reach only tide.ts:542's configured-tide.labels arm (genuinely new: mergeGateLabels.test.ts only configures missing_labels).
- Keep
tideLabelsConfigured.test.ts:71–84(a configured[lgtm]replaces the OWNERS default and the tree is never read). Drop:57–69(missing approvedis covered by bundle.test.ts:561) and:86–97/:99–110(wildcard and case-insensitive matching go throughmatchesLabelPattern, driven bymergeGateLabels.test.ts:50). :1–55copymergeGateLabels.test.ts:1–48almost line for line. Add the kept case to that file instead.
…2) through dist/index.js No bundle scenario configured a valid tide.labels list, so loadTide's probe-skip arm sat at 0 in the e2e coverage run (coverage-e2e/lcov.info BRDA:542,83,1,0) and every 'missing <pattern>' verdict came from the default lists. Add one scenario to mergeGateLabels.test.ts, which already carries the pull_request labeled scaffold: - [lgtm] on an OWNERS-bearing base: merges without reading the tree (the configured list replaces the [lgtm, approved] default) The 'missing approved' verdict is covered by bundle.test.ts, and wildcard and case-insensitive matching go through matchesLabelPattern, already driven by the missing_labels case in the same file. Refs #466 Co-authored-by: quality <quality@hive.kubestellar.io> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Bob Killen <bkillen@linuxfoundation.org>
7473883 to
1a4eb49
Compare
|
Addressed review: dropped the |
🔒 Hold-gate integrity: branch changed while hold-gated — fresh review requiredThis PR's branch moved while it sat hold-gated: the head recorded when the hold was applied was Commits not present in the hold-time snapshot (1):
Authors not in the hold-time author set: A human should review the FULL diff at the current head — a rebase or force-push renames every commit, so everything above needs eyes even if it looks familiar. Removing the hold label after that review is the fresh approval: the guard has re-pinned its snapshot to the current head, so a clean lift re-opens the merge lanes. |
Test Improvement
Adds one scenario to
__tests__/bundle/mergeGateLabels.test.tsdrivingloadTide's configured-tide.labelsarm (src/plugins/tide.ts:542,config.tide.labels === undefinedfalse) through the compileddist/index.js, on apull_requestlabeledevent withtide:\n labels: [lgtm]inprow.yaml:[lgtm]on a base whose tree carries a rootOWNERS→merged pr #1(squash) and the tree is never read — the configured list replaces the[lgtm, approved]defaultThis is the "replaces the default list" / "skipped entirely when
tide.labelsis configured" promise indocs/automatic-merging.md:317-340that was previously unit-only. Themissing approvedverdict is already covered bybundle.test.ts, and wildcard / case-insensitive matching goes throughmatchesLabelPattern, already driven by themissing_labelscase in the same file.Test-only change; no
src/ordist/edits.Related Issue
Refs #466