tc39/ecma262

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

Open

#3,673 opened on Aug 15, 2025

View on GitHub
 (0 comments) (1 reaction) (0 assignees)HTML (15,626 stars) (1,409 forks)batch import
good first issuemeta

Description

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.

Contributor guide

Tech stack
github actions
Domain
ci cddeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitHub Actions workflow syntaxunderstanding of ECMAScript specification IDs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
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.