Where: scripts/check_em_dash.py:24:
SCAN_EXT = {".md", ".py", ".js", ".html", ".css"}The gap: YAML is never scanned at all, even though the repo's own em-dash-free convention is meant to apply repo-wide (CONTRIBUTING.md's style rule isn't scoped to specific file types). Two tracked .yml files already contain a real em dash, un-flagged by CI: .github/ISSUE_TEMPLATE/new_audit.yml and .github/ISSUE_TEMPLATE/new_explainer.yml (both use it inside a checkbox label demonstrating the banned character itself - the same legitimate reason CONTRIBUTING.md is already in ALLOWLIST).
Suggested fix: add .yml/.yaml to SCAN_EXT, and add those two issue-template files to ALLOWLIST alongside CONTRIBUTING.md, with the same justification comment (they're intentionally demonstrating the banned character, not violating the rule).
Where:
scripts/check_em_dash.py:24:The gap: YAML is never scanned at all, even though the repo's own em-dash-free convention is meant to apply repo-wide (CONTRIBUTING.md's style rule isn't scoped to specific file types). Two tracked
.ymlfiles already contain a real em dash, un-flagged by CI:.github/ISSUE_TEMPLATE/new_audit.ymland.github/ISSUE_TEMPLATE/new_explainer.yml(both use it inside a checkbox label demonstrating the banned character itself - the same legitimate reasonCONTRIBUTING.mdis already inALLOWLIST).Suggested fix: add
.yml/.yamltoSCAN_EXT, and add those two issue-template files toALLOWLISTalongsideCONTRIBUTING.md, with the same justification comment (they're intentionally demonstrating the banned character, not violating the rule).