Play your own Switch games on iPhone/iPad — one-click macOS app, no terminal. | 把 Switch 游戏装进 iPhone:图形界面一键构建,不用命令行。Bring your own game.
Swift apple-siliconcustom-formathomebrewiosipaipadipadosiphonemetalnative-portnintendo-switchnxnativeromfsswitch-games
CONTRIBUTING: the 48-hour rule is for the maintainers' own features
v0lumehib224be32f8f5
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.mdindex 7162bec6..d407d366 100644--- a/.github/copilot-instructions.md+++ b/.github/copilot-instructions.md@@ -5,8 +5,7 @@ Read [AGENTS.md](../AGENTS.md) (the fork's, at the root) and [CONTRIBUTING.md](.- `frontend/` and `frontend-qt/` are this fork's own: change them directly. `cd frontend && swift test` is the check.- The engine (`dm/`, `scripts/`, `docs/`, `ref/`) is not in this repository: it is seedds/nxnative at `.upstream-ref` plus `patches/`, built into `engine/` by `python3 tools/engine.py sync`. Do not add files under those paths in a PR (the `pr-scope` check fails it). A change to the engine is a pull request to seedds/nxnative first, and a patch in `patches/` (a commit in `engine/`, then `python3 tools/engine.py export`) only while the fork has to carry it.- Never touch the shader translation chain (`dm/gfx/tools/dmsh_*`, `dm/gfx/nvn/dmsh_chain.h`, `dmsh_chain.lock`, the translator).-- A fix merges when CI is green, unless a maintainer's "changes requested" review is unanswered. A plain review comment does not block. The maintainer who requested the changes reviews again after your push. The owner decides only when the maintainers disagree. A feature PR waits 48 hours for the owner before it merges. Whoever merges a patch renumbers it from `patches/series` on `main`, so do not rebase to chase free numbers. Releases (version bumps, tags, update-history rows) are the owner's.-- No AI attribution anywhere: no "Generated with", no `Co-Authored-By` for a tool, in commits, PRs or issues.+- A fix merges when CI is green, unless a maintainer's "changes requested" review is unanswered. A plain review comment does not block. The maintainer who requested the changes reviews again after your push. The owner decides only when the maintainers disagree. A feature PR from a maintainer waits 48 hours before it merges. A feature from outside never merges by waiting: a maintainer has to agree to the idea, try the app and review the code. A fix from outside gets the same maintainer check before it merges. Whoever merges a patch renumbers it from `patches/series` on `main`, so do not rebase to chase free numbers. Releases (version bumps, tags, update-history rows) are the owner's.- Never attach or commit keys, game files or anything extracted from a game.- You work on a Linux runner and cannot build or run the macOS app. The macOS jobs of `tests.yml` are the check: do not claim a Swift or Metal change works until they are green.- A PR that changes the launcher needs before and after screenshots. You cannot capture them on a Linux runner: say so under Screenshots and ask for them in the PR (CONTRIBUTING.md, "For AI agents and other tools").diff --git a/.github/pull_request_template.md b/.github/pull_request_template.mdindex 87ed250c..dfbfd1a2 100644--- a/.github/pull_request_template.md+++ b/.github/pull_request_template.md@@ -2,7 +2,7 @@## Fix or feature-<!-- Tick one. A fix merges when CI is green and no "changes requested" review is open, a feature after 48 hours. A patch is renumbered at merge. Maintainers label it `bug` or `enhancement`. -->+<!-- Tick one. A fix merges when CI is green and no "changes requested" review is open, a maintainer's feature after 48 hours. An outside PR merges after a maintainer tried it and reviewed it. A patch is renumbered at merge. Maintainers label it `bug` or `enhancement`. -->- [ ] Fix- [ ] Featurediff --git a/AGENTS.md b/AGENTS.mdindex 16f8aab7..d370f8c9 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -7,6 +7,6 @@ This is the fork's guide. The engine has its own, upstream's: [engine/AGENTS.md]- **Here first, upstream in parallel.** A fix to the engine, to a game profile or to upstream's docs may land here first, as a patch. The same change goes to seedds/nxnative as a pull request in parallel, from a branch off their main (`git -C engine fetch seedds`, `engine/` has the remote). If you cannot open that pull request, a maintainer sends it. A patch here is a bridge until upstream has it, and the next bump drops it once the change is in. [patches/README.md](patches/README.md#here-first-upstream-in-parallel) has the rule and the `Upstream-Status` values.- **How a commit in `engine/` becomes a patch.** Work in `engine/` (it holds upstream's tree with our patches as commits on top): change, test, commit with a message that says what and why. `python3 tools/engine.py export` turns the commits made since the last sync into `patches/NNNN-*.patch` with the header `Upstream-Status`, `Reason` and `Issue` (fill them in, `--status`, `--reason` and `--issue` set them) and adds them to `patches/series`. `python3 tools/engine.py check` must pass (headers, no patch on the shader chain, the series applies to the pin). The same commit goes to seedds/nxnative as a pull request in parallel. The patch says `pending` until that pull request is open, then `forwarded seedds/nxnative#<n>`. Commit `patches/` in a PR here. `sync` never throws away work in `engine/`: it stops and names `export`.- **Never add engine files to this repository.** Files under `dm/`, `scripts/`, `docs/` and `ref/` at the root are ignored by `.gitignore`, and the `pr-scope` check fails a PR that adds them. A direct edit of engine files is lost on the next sync.-- **Issues and pull requests.** Follow [CONTRIBUTING.md](CONTRIBUTING.md), section "For AI agents and other tools", and the forms and the PR template in `.github/`. Fix or feature: every fix goes through a PR and merges when CI is green, unless a maintainer's "changes requested" review is unanswered (a plain review comment does not block, and Andy decides only when the maintainers disagree), a feature after 48 hours, a patch is renumbered by whoever merges it, releases and version bumps are the owner's. No AI attribution in commits, PRs or issues. Never attach or commit keys, game files or data extracted from a game.+- **Issues and pull requests.** Follow [CONTRIBUTING.md](CONTRIBUTING.md), section "For AI agents and other tools", and the forms and the PR template in `.github/`. Fix or feature: every fix goes through a PR and merges when CI is green, unless a maintainer's "changes requested" review is unanswered (a plain review comment does not block, and Andy decides only when the maintainers disagree), a maintainer's own feature after 48 hours (a feature from outside never merges by waiting, a maintainer has to agree, try the app and review the code), a patch is renumbered by whoever merges it, releases and version bumps are the owner's. Never attach or commit keys, game files or data extracted from a game.- **Checks.** `cd frontend && swift build && swift test` for the Mac launcher (its tests read `engine/`, so sync first), `python3 -m unittest discover -s frontend-qt/tests` for the Qt front end (and `python3 frontend-qt/gen_localization.py` leaves `frontend-qt/nspb_qt/localization.py` unchanged), `python3 -m unittest discover tools/tests` for the tools. The engine's own tests run in `engine/` as `tests.yml` does.- **Language and text.** Everything is in English except the Chinese pages (`*.zh-CN.md`) and the launcher's strings. No semicolons in UI strings, READMEs and docs.diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex 33663af5..a31b09db 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -59,13 +59,13 @@ A PR that waits on its author for 30 days is closed with a note that it can be r### When a PR merges-This holds for every PR. A PR from outside also gets the check above.+This holds for every PR. A PR from outside also gets the maintainer check above, and never merges before it.Every fix goes through a PR. A fix merges when CI is green. No approval is needed.An unanswered review with changes requested from a maintainer blocks the merge. A plain review comment does not block. The maintainer who requested the changes reviews again once the fix is pushed, and approves or withdraws the request. Each maintainer clears their own objections. If the two maintainers disagree about an objection, Andy ([@LNPANDY](https://github.com/LNPANDY)) decides.-A feature merges after 48 hours.+A feature from the maintainers (v0lumehi and LNPANDY) merges after 48 hours. A feature from outside never merges by waiting. It merges after a maintainer agreed to the idea, tried the app and reviewed the code.A patch in `patches/` takes the next free number from `patches/series` on `main` at merge time. Whoever merges renumbers the patch and notes it in the PR. You do not need to rebase to chase free numbers.diff --git a/CONTRIBUTING.zh-CN.md b/CONTRIBUTING.zh-CN.mdindex 38982d2a..2952abe8 100644--- a/CONTRIBUTING.zh-CN.md+++ b/CONTRIBUTING.zh-CN.md@@ -37,12 +37,12 @@ PR 如果等待作者回复满 30 天,会被关闭,并附一条说明,之### PR 何时合并-以下对所有 PR 都适用。来自外部的 PR 还要先经过上面的检查。+以下对所有 PR 都适用。来自外部的 PR 还要经过上面的维护者检查,检查之前绝不合并。每个修复都通过 PR 提交。修复在 CI 通过后合并,不需要批准。维护者提出的、尚未处理的“要求修改”审查会阻止合并。普通的审查评论不会阻止。推送修复后,提出要求的维护者会再次审查,批准或撤回该要求。每位维护者清除自己的异议。如果两位维护者对某个异议有分歧,由 Andy([@LNPANDY](https://github.com/LNPANDY))决定。-功能在 48 小时后合并。+维护者(v0lumehi 和 LNPANDY)的功能在 48 小时后合并。来自外部的功能不会靠等待合并,要在维护者认可想法、试用应用并审查代码之后才合并。`patches/` 中的补丁在合并时取 `main` 上 `patches/series` 的下一个空闲编号。执行合并的人负责重新编号,并在 PR 中注明。你不需要为了追空闲编号而反复 rebase。