fix: refresh_stale knows the romfolders area

check_freshness gained a romfolders area and refresh_stale did not:
its rows were dropped from a saved report without a word, and --only
romfolders was refused. A rom-folder pin is moved by hand, so the area
is listed for a human, a test holds the two area lists equal, and the
--only help names every area.
This commit is contained in:
Abdessamad Derraz committed 2026-11-06 08:56:14 +01:00
1 parent ea58f6f5ce
commit 8b7e5ceef4
3 files changed
+22 -4

No files matched your search

+4 -1
View File
@@ -760,7 +760,10 @@ committed.
Rows that need a decision are listed and never run: a buildbot core with no
profile, a new `.info` file, the Redump, No-Intro and TOSEC packs, the CI
pins, and `profile_sync`. A failed scraper leaves its cached original
pins, `profile_sync`, and a rom-folder pin (moved by hand in
`platforms/romfolders/_sources/`, then `python -m scripts.scraper.romfolders
--setup NAME` reads it again). `--dry-run --json` prints the plan as JSON.
A failed scraper leaves its cached original
untouched. Each job writes its output to `tmp/refresh_stale/`, and a GitHub
token is taken from `GITHUB_TOKEN` or from `gh auth token`.