Give needs-review entries a structured open question and surface it

未關閉
#211 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
javascript, node.js
領域
tooling

研究方向

Start with the V9 - Deprecated: rule in site/checks.mjs and the age-only sorting in site/lib/reverify.mjs (lines 23-31), then see where needs-review is documented in CONTRIBUTING.md. Done means every needs-review entry carries a - Review: line that the checks enforce, the question appears on the entry page and in data.json, and the monthly re-verify issue lists them. The open decision on grandfathering existing entries needs a maintainer answer before implementing. Run npm run check to verify.

由索引模型根據 Issue 內容生成。

描述

enhancement priority: medium

Summary

43 entries are needs-review, none with a machine-readable statement of what is unresolved. deprecated requires a - Deprecated: line (V9); needs-review has no equivalent. The re-verify batch sorts by age only, so a recently checked needs-review entry waits months and contributors never see its question.

Related: #99

Where

  • CONTRIBUTING.md:16
  • site/lib/reverify.mjs:23-31
  • site/checks.mjs (V9 - Deprecated: rule)

Suggested fix

  • Add a - Review: marker line, enforced the way V9 is.
  • Show it on the entry page and in data.json.
  • Append an "Open questions" section to the monthly re-verify issue.

Open question: grandfather existing entries for one cycle while backfilling?

Acceptance criteria

  • Every needs-review entry states its open question
  • The re-verify issue lists them

Getting started

  • Relevant files: site/checks.mjs, site/lib/reverify.mjs, site/lib/entry-page.mjs
  • How to run tests: npm test (unit tests), npm run check (tests + validate + build). Node 22+, no dependencies.
  • Related docs: site/README.md, CONTRIBUTING.md

Filed by repo-audit/full-audit at 982fcd9. Severity: medium. Effort: M. audit-key: enhancement|site/checks.mjs|needs-review-marker

主要語言
JavaScript
星號
58
分支
15
平均合併
1 天 14 小時
30 天內合併 PR
11

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/Free-Game-Dev-Assets 的其他 Issue

查看 TMHSDigital/Free-Game-Dev-Assets 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。