ci: run game-free regressions on Windows and Linux #149

Merged

monsterlag merged 1 commit from ci/game-free-checks into main

2026-11-07 14:02:54 +00:00

monsterlag commented

2026-11-07 13:28:05 +00:00

(Migrated from github.com)

The workflow uses pinned actions, a read-only token, and disposable GitHub-hosted runners. It needs no game, native build, SDK, secrets, uploaded artifacts, or cache. Changed pull requests cancel their superseded runs; main and manual runs keep their current run.

Validation: the same 21 extraction/recovery tests and six cache tests passed on both platforms in the fork run. Those three source/test files are identical to the adopted upstream revision; the latest upstream builder-cache suite also passes locally after its separate profile-handling change. The proposed trigger configuration passed independent read-only review and whitespace checks; upstream scheduling remains to be observed on this PR.

These jobs are path-filtered, so they should not be made universally required for unrelated pull requests without an always-running companion check. Fork-run approval, if requested by GitHub, remains with the maintainer.

The extraction and builder-cache regression suites are now upstream, but future changes do not run them automatically. Run both suites on Windows 2022 and Ubuntu 24.04 with Python 3.12 for relevant main-branch pushes and pull requests, plus manual runs. The workflow uses pinned actions, a read-only token, and disposable GitHub-hosted runners. It needs no game, native build, SDK, secrets, uploaded artifacts, or cache. Changed pull requests cancel their superseded runs; main and manual runs keep their current run. Validation: the same 21 extraction/recovery tests and six cache tests passed on both platforms in [the fork run](https://github.com/monsterlag/Hookshot/actions/runs/42375362397). Those three source/test files are identical to the adopted upstream revision; the latest upstream builder-cache suite also passes locally after its separate profile-handling change. The proposed trigger configuration passed independent read-only review and whitespace checks; upstream scheduling remains to be observed on this PR. These jobs are path-filtered, so they should not be made universally required for unrelated pull requests without an always-running companion check. Fork-run approval, if requested by GitHub, remains with the maintainer.

Commenting is not possible because the repository is archived.

No reviewers