Skip to content

Play your own Switch games on iPhone/iPad — one-click macOS app, no terminal. | 把 Switch 游戏装进 iPhone:图形界面一键构建,不用命令行。Bring your own game.

Release notes rules: drop an unasked bullet, tidy the AGENTS line

v0lumehi1795649bbbc7
diff --git a/AGENTS.md b/AGENTS.md
index 684213c8..8bf89f85 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -12,4 +12,4 @@ This is the fork's guide. The engine has its own, upstream's: [engine/AGENTS.md]
- **Merging with admin rights.** An admin merge never goes over a red check. That holds even when @LNPANDY overrides an objection. If a re-review is slow, the other maintainer pings the reviewer and does not merge with admin rights.
- **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. The pre-commit hook runs `python3 tools/engine.py check` when `patches/` or `.upstream-ref` is staged. The pre-push hook runs the checks above for the files the push changes, `tools/githooks.py` has the list. Fix the failure, do not bypass the hook.
- **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.
-- **Release notes.** Release notes follow `.github/release_notes_template.md`, English first, no emojis.
+- **Release notes.** They follow `.github/release_notes_template.md`, English first, no emojis.
diff --git a/RELEASING.md b/RELEASING.md
index 9dc5dc36..2fd48a44 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -62,7 +62,6 @@ CI writes a short body: the version and the tested candidate. The readable notes
- People are written as `@login`, the owner as `@LNPANDY`.
- Every claim comes from the changelog row, the merged pull requests or the issues. Nothing is invented.
- Write the notes before the final tag is pushed or right after it. Put them in a file and publish with `gh release edit <tag> --notes-file <file>`. Never paste them from a chat, that brings emojis along.
-- The notes of a published release stay as they are, unless a fact in them is wrong.
## Who tags