Repository navigation
Conversation
This was referenced Oct 26, 2026
v0lumehi
force-pushed
the
infra-templates
branch
from
October 27, 2026 09:19
a957e6b to
0edb7fa
Compare
This was referenced Oct 27, 2026
README points players to NX2Apple at the top; docs/frontends.md says what a front end builds on
#387
Merged
The bug report form asks up front for what a problem is traced with: - the nxnative commit and the shader chain version; - the game's title ID and version, the device and OS; - how it was built and run, and any environment overrides; - the whole log, with where each build writes it. Issue seedds#242 needed a second round for the commit, the log and the macOS version. The game request form points at the NSP script's survey. Both forms refuse game files and keys. The PR template asks what was checked (tests, games, devices) and whether the docs and the symptom index followed. For a change to the chain, the host or a tool every game uses, it asks which games were run beyond the one it was made for. CONTRIBUTING.md links AGENTS.md and docs/development.md instead of repeating them. It covers reporting, no game files, where findings go, the chain header, local GPU tests, and how changes get in. README's For developers section links it.
…rms first (a new platform, a second implementation of an existing path, or more than about 1,000 lines), one concern per PR, and the supported devices as README names them
…n issue Requests and PRs for graphical front ends keep coming in (seedds#104, seedds#244, seedds#264, seedds#332, seedds#374), although README names NX2Apple, a community app that packs games, keeps a library and starts them with their settings. The mention sits in "Pack an IPA", where someone about to build a front end does not look. The issue chooser now lists NX2Apple first among its links, so it shows before any form opens. A feature request form says that a new front end is a project of its own and what is welcome here instead: the piece a front end needs from nxnative. CONTRIBUTING.md has a section on graphical front ends: the interfaces one builds on (the NSP script's --progress json events, the settings list a built app carries, environment switches), and that the settings screen inside the iPhone app is part of nxnative.
v0lumehi
force-pushed
the
infra-templates
branch
from
October 27, 2026 12:09
0edb7fa to
71a98fe
Compare
seedds
added a commit
that referenced
this pull request
Oct 27, 2026
Most bug reports reached the maintainer without what a problem is traced with, so the first reply asked for it (#242, #155). The bug report form asks for the game with its title ID and version, the nxnative commit, the shader chain version, how it was built and run, the device and OS, the settings and environment overrides, and the whole log. A game request form points at the NSP script's survey, a feature request form at front ends' own projects, and the issue chooser at NX2Apple first. CONTRIBUTING.md says how a change gets in: one change per PR, where findings go, the shader chain's header, the tests CI cannot run, scope agreed first for large changes and other platforms, the supported devices as README names them, front ends as separate projects building on docs/frontends.md, and that the maintainer often takes a PR in as a reworked commit crediting its author. README's For developers line links it. Updated while landing: front ends can also keep a player's choices in the app's saved choices; the Mac settings window is part of nxnative like the iPhone's screen; a Mac app's env.txt location in the bug form; the PR template asks for the regress.py report AGENTS.md requires; a conflicting PR may be rebased by the maintainer while taking it in. Co-authored-by: v0lumehi <[email protected]>
Owner
|
Thanks, @v0lumehi. This landed on
The four forms parse as YAML, and |
seedds
added a commit
that referenced
this pull request
Oct 27, 2026
…306) 81d53bf's message lists updates made while landing #306, but they were left unstaged when it was committed, so main got #306 as it was. These are those updates: front ends can also keep a player's choices as saved choices; the Mac settings window is part of nxnative like the iPhone's screen; the bug form names settings changed in the Mac window, a Mac app's env.txt and variables a front end sets; the PR template asks for the regress.py report AGENTS.md requires, with an absolute link that works inside a PR; a conflicting PR may be rebased by the maintainer. The three issue forms also drop labels: [], which GitHub's issue-forms schema (SchemaStore github-issue-forms.json) rejects: labels is a non-empty list or a string when present. All four files now validate against it and config.yml against github-issue-config.json. Co-authored-by: v0lumehi <[email protected]>
Owner
|
Correction: the updates my comment above lists were not in 81d53bf. I left them unstaged when I committed, so 81d53bf is this PR exactly as you wrote it. They landed in 1289f16, which also drops |
This was referenced Oct 27, 2026
v0lumehi
added a commit
to v0lumehi/nxnative
that referenced
this pull request
Oct 30, 2026
…API skip The pull request template and the issue forms from seedds#306 only appear on GitHub's web pages. gh pr create, gh issue create and the API open a PR or an issue with whatever body they are given, so an agent never sees them and nothing told it to follow them: PRs and issues opened by agents came in with their own structure, without the Checked and Docs sections or the bug form's commit, chain version and device. 06-dev-loop.md gets a section 8, "Opening an issue or a pull request": a PR body keeps the template's three sections (What and why, Checked, Docs with its checkboxes), an issue the matching form's fields as headings in their order, and nothing from a game in either. AGENTS.md's task table points there (AGENTS.md stays at its 1,500 words), and CONTRIBUTING.md says the same for people who open them from the command line. Checked: test_docs passes (links, anchors, word limits).
Know-It-All-Brother
pushed a commit
to Know-It-All-Brother/nxnative
that referenced
this pull request
Nov 9, 2026
…eedds#388) Most bug reports reached the maintainer without what a problem is traced with, so the first reply asked for it (seedds#242, seedds#155). The bug report form asks for the game with its title ID and version, the nxnative commit, the shader chain version, how it was built and run, the device and OS, the settings and environment overrides, and the whole log. A game request form points at the NSP script's survey, a feature request form at front ends' own projects, and the issue chooser at NX2Apple first. CONTRIBUTING.md says how a change gets in: one change per PR, where findings go, the shader chain's header, the tests CI cannot run, scope agreed first for large changes and other platforms, the supported devices as README names them, front ends as separate projects building on docs/frontends.md, and that the maintainer often takes a PR in as a reworked commit crediting its author. README's For developers line links it. Updated while landing: front ends can also keep a player's choices in the app's saved choices; the Mac settings window is part of nxnative like the iPhone's screen; a Mac app's env.txt location in the bug form; the PR template asks for the regress.py report AGENTS.md requires; a conflicting PR may be rebased by the maintainer while taking it in. Co-authored-by: v0lumehi <[email protected]>
Know-It-All-Brother
pushed a commit
to Know-It-All-Brother/nxnative
that referenced
this pull request
Nov 9, 2026
…eedds#306) 87311ff's message lists updates made while landing seedds#306, but they were left unstaged when it was committed, so main got seedds#306 as it was. These are those updates: front ends can also keep a player's choices as saved choices; the Mac settings window is part of nxnative like the iPhone's screen; the bug form names settings changed in the Mac window, a Mac app's env.txt and variables a front end sets; the PR template asks for the regress.py report AGENTS.md requires, with an absolute link that works inside a PR; a conflicting PR may be rebased by the maintainer. The three issue forms also drop labels: [], which GitHub's issue-forms schema (SchemaStore github-issue-forms.json) rejects: labels is a non-empty list or a string when present. All four files now validate against it and config.yml against github-issue-config.json. Co-authored-by: v0lumehi <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update: rebased on
main349abd0. README's For developers line keeps both links (Front ends from #387, CONTRIBUTING.md from here), and CONTRIBUTING's front-end section now linksdocs/frontends.md, which #387 brought in.Part of #388 (front ends: one interface between the engine and graphical apps).
Issue forms and a PR template that ask for what a report is traced with
Update (2026-10-27): rebased on
main. The last commit adds the NX2Apple link, the feature request form and the front-end section, because front-end requests keep coming in (#104, #244, #264, #332, #374). #387 does the same in README and documents the interface.Most bug reports reach the maintainer without what a problem is traced with, so the first reply asks for it. In #242 (Breath of the Wild, corrupted picture on an M5), the report had a careful diagnostic summary but no nxnative commit, no macOS version, no environment settings and no full log; the first reply had to ask for all four, plus the shader-build log. #155 and others went the same way.
This adds templates for issues and pull requests, and a short CONTRIBUTING.md. Nothing in the code changes.
.github/ISSUE_TEMPLATE/bug_report.yml, an issue form. The required fields:git rev-parse --short HEAD);DMSH_CHAINindm/gfx/nvn/dmsh_chain.h, or theb-<version>folder);env.txt,DM_*), "none" if none;~/Library/Logs/nxnative/<title ID>.logand.prev.log, the terminal output, the iPhone'slog.txtandlog.prev.txt, anddmsh_build.logfor graphics problems.A required checkbox confirms that nothing attached contains game files, keys or data extracted from a game.
.github/ISSUE_TEMPLATE/game_request.yml. It points at the NSP script's survey (survey.md) as the most useful attachment, and asks how far the game got..github/ISSUE_TEMPLATE/config.yml. Blank issues stay allowed. The first link is NX2Apple, for anyone looking for a graphical app to pack and play games, so it shows before any form opens. Then links to README.md (packing, playing, logs) and docs/development.md (porting, debugging).3a.
.github/ISSUE_TEMPLATE/feature_request.yml. A short feature request form. Its note says that a new graphical front end is a project of its own (NX2Apple is one), that what a front end needs from nxnative is welcome here, and that large changes agree on their scope first..github/pull_request_template.md.CONTRIBUTING.md. It links AGENTS.md and docs/development.md instead of repeating them. It covers:reporting a problem and never attaching game files;
where to start, and one change per PR off
main;commit messages, where findings go, the chain header, and the local GPU tests (
make -C dm/gfx/tests GAME=<id> run; CI has no Metal 4);that a PR is often taken in squashed or reworked with
Co-authored-byand then closed, which is expected.graphical front ends: an app that packs, lists or starts games is a separate project that builds on nxnative's interfaces (the NSP script's
--progress json, the settings list a built app carries, environment switches); what it needs from nxnative is welcome as an issue or small PR. The settings screen inside the iPhone app is part of nxnative.README's For developers section links it.
Checked
test_docspasses: links and anchors, AGENTS.md and guide word limits.ci.sh(host tests, CPU gfx tests, every gfx test built,dmhostfor three profiles, the iOS compile check, all tool tests): no failures.main; I have not seen them rendered in this repository.