community: enable Discussions, auto-label and welcome external PRs, and state a response time
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github, github-actions, javascript
调研方向
Start with CONTRIBUTING.md and inspect the repository’s existing GitHub Actions workflows and settings; the issue names labeler.yml and CODEOWNERS as proposed additions. Check how first time contributors’ PRs are approved and how the catalog, site, and docs paths are organized. Done means Discussions is enabled, new PRs receive path based labels and a welcome comment, and CONTRIBUTING states the review window.
由索引模型根据 Issue 内容生成。
描述
Why it matters
External contributions are arriving (PRs #48, #52, #78 from three people) but the path is bumpy: PR #78 has been open since 2026-10-16 with no review and no "Validate catalog" run, because first-time-contributor workflows wait for manual approval. Questions ("is this licence OK for…") have nowhere to go but issues, and there is no Discussions tab.
Evidence
gh pr view 78: open since 2026-10-16, no review, checks show only Socket Security; the validate run is inaction_required.gh api repos/TMHSDigital/Free-Game-Dev-Assets→has_discussions: false.CONTRIBUTING.mdsays what to do but not what to expect.
Suggested approach
- Enable Discussions with Q&A, Asset requests and Show and tell (games shipped with catalog assets double as marketing).
- A
labeler.ymlworkflow labelling PRs by path (catalog/**→new-source/correction,site/**→ site,docs/**→ documentation) and a first-PR welcome comment that explains the approval step and links the checklist. - Review the Actions setting for first-time contributors, or document why approval is needed.
- A sentence in CONTRIBUTING on the review window and a
CODEOWNERSfile so review requests are automatic.
Done when
Discussions is on, new PRs get labels and a welcome comment automatically, and CONTRIBUTING states the expectation.
- 主要语言
- JavaScript
- 星标
- 58
- 派生
- 15
- 平均合并
- 16 小时 53 分钟
- 30 天内合并 PR
- 14
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
TMHSDigital/Free-Game-Dev-Assets 的其他 Issue
-
community marketing priority: low
难度 2/5 1-3 小时 新手友好度 72/100
TMHSDigital/Free-Game-Dev-Assets#151 ·
维护者通常 1 天内回复
-
documentation priority: medium
难度 2/5 1-3 小时 新手友好度 78/100
TMHSDigital/Free-Game-Dev-Assets#72 ·
维护者通常 1 天内回复
-
enhancement
难度 1/5 1-3 小时 新手友好度 68/100
TMHSDigital/Free-Game-Dev-Assets#3 · 1 条评论 ·
维护者通常 1 天内回复
-
marketing priority: low
难度 2/5 1-3 小时 新手友好度 55/100
TMHSDigital/Free-Game-Dev-Assets#152 ·
维护者通常 1 天内回复
-
feature priority: medium
难度 5/5 一周以上 新手友好度 25/100
TMHSDigital/Free-Game-Dev-Assets#144 ·
维护者通常 1 天内回复
查看 TMHSDigital/Free-Game-Dev-Assets 的全部 Issue
相似的 Issue
-
bug require-triage
难度 2/5 1-3 小时 新手友好度 72/100
expressjs/expressjs.com#2549 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
vercel-labs/agent-skills#348 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
NanmiCoder/dsh-agent-teams#289 ·
维护者通常 1 天内回复