tc39/ecma262

issue warning in CI when a previously-defined ID becomes undefined

Open

#3,673 建立於 2025年8月15日

在 GitHub 查看
 (0 留言) (1 反應) (0 負責人)HTML (15,626 star) (1,409 fork)batch import
good first issuemeta

描述

We should add a GitHub CI job that emits a warning on the line of the spec that defines an ID that becomes undefined by the PR.

貢獻者指南

技術棧
github actions
領域
ci cddeveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
GitHub Actions workflow syntaxunderstanding of ECMAScript specification IDs
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
Examine existing CI workflows in the repository, particularly those that validate spec consistency. Understand how IDs are currently defined in the spec (likely in the specification source files). Then implement a GitHub Actions job that runs a script to compare the set of IDs before and after the PR, and emit warnings using the GitHub Actions warning command `::warning file=...,line=...,title=...,message=...` for any ID that becomes undefined. Look at the repository's ecmarkup tools or similar for parsing. The issue references the GitHub Actions warning command documentation for implementation.