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

Open
#3,542 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

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.
Dominant language
Go
Stars
97
Forks
61
Avg merge
4h 14m
Merged PRs (30d)
913

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opensro-dev/opensro

All issues in opensro-dev/opensro

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.