docs(ci): the third disclaimer-close, and the forge binds only the adjacent number #2317
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2317
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1120-2122"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Documentation of a tracker behaviour, not a device spec: no
devices/file is touched, and issue 130 stays open and blocked (Ubiquiti publishes no UDW-PRO artifact; the nine surfaces in that thread are unchanged).What happened. PR #2301 merged at 19:08:34Z with a body opening "Does not close issue 130 or issue 803" (as written there, with
#before each number). Issue 130 went toclosedat 19:08:37Z with no comment on it; 803 stayed open. So the forge read the first number after the keyword and ignored the second:oris not a separator in its run. The issue was reopened at 21:24Z with that measurement recorded.What changes.
docs/CI.mdscripts/check-closing-keywords.jsThe checker was run against the #2301 sentence: it reports exactly one at-risk reference (
#130,negated) and not the second, which matches what the forge did.Gates:
node scripts/syntax-check.js-> 498 files, all OK;node scripts/audit-port-types.js-> 0 gated, 2704 reported template ports (unchanged baseline).Refs #130