Update arena configs from maDisplayTools - #169
Conversation
|
Closing as superseded by #172. This PR's entire diff is the #172 removes the timestamp so the generated file is a pure function of the input YAML. Verified by dispatching the sync workflow on that branch: it fetched the configs from Nothing is lost by closing this — the arena config content here is identical to |
scripts/generate-arena-configs.js stamped `Last updated: <new Date()>` into the generated header, so js/arena-configs.js changed on every run regardless of whether any arena YAML had changed. The sync-arena-configs workflow's "Check for changes" step was therefore always true, and the workflow opened a PR every Sunday whose entire diff was that one timestamp line (#169, and the merged #158/#147/#122/#117 before it). Drops the timestamp so the output is a pure function of the input YAML. The generator is now byte-idempotent (verified: three consecutive runs produce an identical file), which makes "Check for changes" mean an actual config change. Git history already records when the file last changed. js/arena-configs.js is regenerated here; it is prettier-ignored by design (LAB-111 follow-up) and the diff is the removed header line only. Regenerated from configs fetched the same way the workflow fetches them (GitHub contents API against reiserlab/maDisplayTools), so the next CI run reproduces this file byte-for-byte and reports no changes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 participant
Automated Arena Config Sync
This PR was automatically generated by the
sync-arena-configsworkflow.Source:
maDisplayTools/configs/arenas/+configs/arena_registry/index.yamlChanges
The
js/arena-configs.jsfile has been regenerated from the latest YAML configs in maDisplayTools.Review Checklist