Infrastructure: stop the queued bot cycle, one source check at a time, track site/ (#27)
CI / test (pull_request) Successful in 39s

- bot-cycle.yml: no schedule. It needs a runner on the bot's machine that no one has added, so every 4 hours
  a run queued forever. The bot's data already arrives through the daily source check (it reads
  DragonKind/DragonKind) and the model goes back through push-policy. Still runnable by hand.
- update-sources.yml: a concurrency group, so two dispatches never build and push at once.
- .gitignore: drop `/site` (a Python template's mkdocs line). site/ is the Atlas page; new files there were
  silently ignored.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
This commit is contained in:
2026-11-19 15:16:59 +00:00
co-authored by Claude Opus 5.5
parent d0141f2d9c
commit 5f080e0a82
3 changed files with 9 additions and 4 deletions
+4 -2
View File
@@ -10,9 +10,11 @@
# DK_ACCOUNT_SALT the salt account names are hashed with (the same one every time)
# ATLAS_BOT_TOKEN as in update-sources.yml
name: Bot cycle
# Not scheduled: no runner has the `bot-host` label yet (issue #27), and the bot's data already arrives through the
# daily source check. Put the schedule back once Ken adds a runner on the bot's machine:
# schedule:
# - cron: "41 */4 * * *"
on:
schedule:
- cron: "41 */4 * * *"
workflow_dispatch:
jobs:
cycle: