Audit: merged PRs list "not ported / left open" items with no issue; every open item must name its issue

未关闭
#3,542 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
20/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
领域
documentation

调研方向

Start with the eight merged PRs listed in the body (#3496, #3493, #3472, #3455, #3437, #3426, #3424, #3421) and read each one's "not ported / left open" section. For every real gap, open a separate issue and link it back from the PR; for every non-gap, leave a one-line reason in a PR comment. Then update AGENTS.md and CONTRIBUTING.md so every item a PR leaves open names its issue or the reason it needs none.

由索引模型根据 Issue 内容生成。

描述

area: ops bug documentation priority: high

Owner (2026-11-15): "we are porting the full game ... if not ported, where is the separate GH issues opened? or we forget forever?"

Merged PRs whose bodies list open items with no issue reference

#3496, #3493, #3472, #3455, #3437, #3426, #3424, #3421. (#3507's four points are covered by #3522.)

Done when

  • Each listed item is read; a real gap gets its own issue (linked back from the PR), a non-gap gets a one-line reason in a PR comment.
  • AGENTS.md / CONTRIBUTING.md: every item a PR leaves open names its issue, or the reason it needs none.
主要语言
Go
星标
97
派生
61
平均合并
4 小时 14 分钟
30 天内合并 PR
913

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

opensro-dev/opensro 的其他 Issue

查看 opensro-dev/opensro 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。