kmoody/libretro
1
0 Fork 0
mirror of https://github.com/Abdess/retroarch_system.git synced 2026-10-29 07:07:20 -05:00
Code Issues Packages Projects Releases Wiki Activity

chore: merge audit fixes (tests)

Browse Source
This commit is contained in:
Abdessamad Derraz committed 2026-10-21 05:44:32 +02:00
2 parents 82acd55ebc 53121c1a5d
commit e03fe338ee
7 files changed
+185 -37
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

wiki/testing-guide.md
+4 -2
View File
@@ -299,8 +299,10 @@ files it points at gives the installer a 404.
The `validate.yml` workflow runs `python -m unittest discover -s tests -t . -v` on both
roads into main: every pull request, and every direct push, that touches
`bios/`, `platforms/`, `emulators/`, `schemas/`, `scripts/`, `tests/` or
`install.py`. Work reaches main by push as often as by pull request, so a suite
`bios/`, `platforms/`, `emulators/`, `schemas/`, `scripts/`, `tests/`,
`install.py` or an input of the site build such as `wiki/`. The same job then
builds the site with `mkdocs build --strict`, so a page that would fail the
deploy fails the pull request. Work reaches main by push as often as by pull request, so a suite
wired to pull requests alone would guard the road nobody takes. The test job
(`run-tests`) runs in parallel with schema validation, and on a pull request
with BIOS validation and auto-labeling too. Those two read pull request context