- Scraper (statcheck-elo-scraper/refresh_elo.py) downloads the stat-check
ELO workbook from OneDrive and builds public/elo-data.json
- GitHub Actions workflow (.github/workflows/refresh-elo.yml) runs daily
at 06:00 UTC and commits updated ELO data
- Frontend fetches elo-data.json and matches players by name, using BCP
career event history to disambiguate same-name candidates
- ELO score shown in new sortable Stat-Check ELO column, visible on all
screen sizes; unmatched players show —
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
stat-check.com's ELO data is behind Microsoft auth with no public
API or download endpoint available. Removing the sync script,
placeholder JSON, CI job, table column, and all related JS.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- scripts/sync-elo.py: downloads Excel sheet, auto-detects columns,
writes public/elo-data.json keyed by lowercase player name
- .gitlab-ci.yml: sync-elo stage (schedules only) commits the JSON
then a normal push pipeline handles build + deploy; build/deploy
skip on scheduled runs to avoid double deployment
- index.html + main.js: ELO Rank column with sort support; loads
elo-data.json asynchronously and re-renders when ready; fails
silently if data is missing
Requires one-time setup:
1. GitLab project token (write_repository) stored as GITLAB_PUSH_TOKEN
2. Pipeline schedule: cron 0 2 * * 3 (Wednesday 02:00 UTC) on main
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
GitLab CI
mandaloreandClaude Sonnet 4.6