3 Commits

Include renames

Author	SHA1	Message	Date
mandaloreandClaude Opus 5.5	a8cb306f88	Push ELO refresh with the PAT so it triggers the 40k deploy ... actions/checkout persists GITEA_TOKEN as an http.extraheader, which takes precedence over the token in the remote URL. Gitea doesn't fire workflows for pushes made with GITEA_TOKEN, so the refreshed data never deployed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-22 16:34:24 -05:00
mandaloreandClaude Sonnet 5	b726d1c8ec	Rename secret reference to SYNC_ACCESS_TOKEN ... Gitea rejects secret names starting with GITEA_ (reserved for its own built-in secrets). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-22 15:17:47 -05:00
mandaloreandClaude Sonnet 5	ba4d71613b	Replace GitLab CI with Gitea Actions workflows ... GitLab CE was migrated off to reduce memory pressure on the host, so .gitlab-ci.yml is dead. Split into one workflow file per site (shared, 40k-rankings, aos-rankings, kingmaker, scouting, events) since Gitea/ GitHub Actions path filters are workflow-level, not job-level like GitLab's rules.changes. Build+deploy are combined into a single job per site rather than separate build/deploy stages, since both run on the same host and there's no need to round-trip artifacts between them. The weekly ELO refresh job's schedule (Wed 02:00 Atlantic/Azores) is approximated as a fixed 02:00 UTC cron, since Actions cron has no DST handling. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-22 15:14:49 -05:00