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.