diff --git a/.gitea/workflows/bot-cycle.yml b/.gitea/workflows/bot-cycle.yml index ca280db..4419b43 100644 --- a/.gitea/workflows/bot-cycle.yml +++ b/.gitea/workflows/bot-cycle.yml @@ -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: diff --git a/.gitea/workflows/update-sources.yml b/.gitea/workflows/update-sources.yml index 8f0000b..57b0c4d 100644 --- a/.gitea/workflows/update-sources.yml +++ b/.gitea/workflows/update-sources.yml @@ -16,6 +16,10 @@ on: schedule: - cron: "23 10 * * *" # daily workflow_dispatch: +# one check at a time: a second dispatch waits instead of building and pushing alongside the first +concurrency: + group: update-sources + cancel-in-progress: false jobs: check: runs-on: ubuntu-latest # a runner label on the server (act_runner) diff --git a/.gitignore b/.gitignore index 3bdc827..38e102a 100644 --- a/.gitignore +++ b/.gitignore @@ -166,8 +166,7 @@ venv.bak/ # Rope project settings .ropeproject -# mkdocs/Zensical documentation -/site +# (mkdocs' /site is not ignored: site/ here is the Atlas page) # mypy .mypy_cache/