dcdpr / jp / 25493778179
66%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 299
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 66.139%. Remained the same
25493778179

push

github

web-flow 
chore(rfd): Add `rfd-require` and `Requires` relationship (#618)

Introduces a new `Requires`/`Required by` metadata pair for RFDs,
complementing the existing `Extends`/`Extended by`. Where `Extends`
captures design lineage, `Requires` captures a hard dependency: the
dependent RFD cannot advance to Accepted (or Implemented) until its
prerequisites reach the required status first.

Both relationships participate in the same promotion gate — extension
implies dependency, so `Extends ⊆ Requires` for enforcement. An RFD
cannot be promoted to Accepted while any `Requires`-or-`Extends` target
is below Accepted; it cannot reach Implemented while any target is below
Implemented. Cycles in the union graph are refused at write time.

`just rfd-require NNN MMM` records that NNN requires MMM, writing
`Requires` on the source and `Required by` on the target. Both sides
accept draft IDs (DNN). A draft-to-published back-link is suppressed at
write time and filled in automatically when the draft is promoted.

The earlier per-command code in `rfd-extend` is replaced by a shared
private `_rfd-link` helper that both `rfd-extend` and `rfd-require`
delegate to. The helper handles draft-aware bidirectional writes, cycle
detection across the union graph, and the duplicate check (the same
target may not appear under both `Requires` and `Extends`).

`rfd-promote` gains the corresponding pre-flight checks: refusing
Draft→Discussion when a dependency reference points to a draft;
enforcing the gate at Discussion→Accepted and Accepted→Implemented; and
backfilling missing `Required by`/`Extended by` back-links on dependency
targets when a draft is promoted to a permanent number.

The VitePress docs loader gains three build-time validations on the
published graph: a no-duplicate check, a status gate, and a DFS cycle
detector on the `Requires ∪ Extends` union graph.

Existing RFDs are backfilled with `Requires`/`Required by` metadata
across ~40 published RFDs and drafts. Duplicate d... (continued)

25603 of 38711 relevant lines covered (66.14%)

185.17 hits per line

Jobs
ID Job ID Ran Files Coverage
1 25493778179.1 299
66.14
 GitHub Action Run
Source Files on build 25493778179