Area
Other
The problem
In issue #41, a user (@metabo7000) lacking technical competence asked for a pre-built firmware with custom VID/PID. The author correctly declined, citing legal concerns around distributing firmware with arbitrary USB identifiers. Users who cannot set up a local toolchain have no accessible way to obtain a custom firmware.
Proposed shape
My template repository nukdokplex/RS-Key-builder addresses this gap. It provides a GitHub Actions workflow that builds RS-Key firmware with user‑selected parameters via workflow_dispatch — no local toolchain required. Users create a repo from the template, configure the build through simple form inputs, trigger the workflow, and download the resulting .uf2 from a Release, then delete the repo.
I propose adding a short section to the RS-Key documentation (e.g. under a "Community builds" or "Alternative build methods" heading) linking to this template. A note should clarify that this method is intended for evaluation and experimentation only, not for production or security‑sensitive use, and that the official build method remains the recommended approach.
Alternatives considered
No response
Area
Other
The problem
In issue #41, a user (@metabo7000) lacking technical competence asked for a pre-built firmware with custom VID/PID. The author correctly declined, citing legal concerns around distributing firmware with arbitrary USB identifiers. Users who cannot set up a local toolchain have no accessible way to obtain a custom firmware.
Proposed shape
My template repository
nukdokplex/RS-Key-builderaddresses this gap. It provides a GitHub Actions workflow that builds RS-Key firmware with user‑selected parameters viaworkflow_dispatch— no local toolchain required. Users create a repo from the template, configure the build through simple form inputs, trigger the workflow, and download the resulting.uf2from a Release, then delete the repo.I propose adding a short section to the RS-Key documentation (e.g. under a "Community builds" or "Alternative build methods" heading) linking to this template. A note should clarify that this method is intended for evaluation and experimentation only, not for production or security‑sensitive use, and that the official build method remains the recommended approach.
Alternatives considered
No response