Repository navigation
Add a reusable shared-drift workflow for the siblings to call - #30
Merged
Merged
Conversation
Each sibling carries its own shared-drift job in ci.yml, and the copies have drifted: only steam-backlog's ci.yml sets permissions:, none pins actions to a SHA or sets timeout-minutes or concurrency. .github/workflows/shared-drift.yml is now the one definition (on: workflow_call): read-only token, SHA-pinned checkout (persist-credentials: false) and setup-python, timeout-minutes: 10, and a job-level concurrency group with its own suffix (a called workflow that reuses the caller's workflow-level group deadlocks). It checks out the caller and runs the caller's own scripts/sync_shared.py: --check always, --check --latest on schedule/workflow_dispatch or with `latest: true`. Inputs: latest (bool), python-version (default 3.11). Reusable workflow over a synced template, with the trade-off in the README: the drift check already fetches from this repo at CI time, so workflow_call adds no new runtime dependency; siblings keep their own triggers; and a sync push never touches .github/workflows/ (no `workflow` token scope needed). The cost is a second pin (the uses: SHA next to shared.lock), which Dependabot bumps once main is tagged. Not wired into any sibling yet (C2). README's schedule section also named a --check-latest flag that doesn't exist; it is --check --latest. actionlint 1.7.7 is clean on the workflow and on a sample caller. Refs #16 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With one group for every event and cancel-in-progress on, a push to main landing while the weekly scheduled run was in flight cancelled its --check --latest, and nothing reran it until the next week. Refs #16 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #16 (shared
shared-driftworkflow). Not wired into any sibling yet: that's C2.Recommendation: reusable workflow (
workflow_call), not a synced templateuses: …@<SHA>per sibling--checksync_shared.py --checkalready fetches from here at CI time, so no new failure modeci.yml.github/workflows/: the pushing token needsworkflowscope (yours has it; future automation might not)github-actionsbumps the SHA +# vXcomment oncemainis tagged (A5)sync_all_siblings.py updateshared.lock+uses:SHA)The two-pin cost is small. The workflow changes rarely, and whatever SHA it's pinned to, it runs the sibling's own
sync_shared.pyagainst the sibling's own lock.Convention change if you accept this: siblings' CI will reference a workflow in this repo by SHA. Workflows do not become synced files.
The workflow
on: workflow_call, inputslatest(bool, default false) andpython-version(default"3.11").permissions: contents: read. A called workflow can only narrow the caller's token.checkout/setup-pythonSHAs are the same pins asci.yml. Checkout usespersist-credentials: false.timeout-minutes: 10.concurrencyis set at job level with a-shared-driftsuffix. In a called workflow,github.workflowis the caller's name, so reusing the caller's workflow-level group would deadlock.sync_shared.py --check, then--check --latestonschedule/workflow_dispatchor whenlatest: true. That's the same behaviour as today's per-sibling jobs.Caller (for C2):
Verification
concurrencyand a typedwith:that calls it locally.Also
README gains a section with the table above. It also fixes the schedule section, which named a nonexistent
--check-latestflag (the flag is--check --latest).🤖 Generated with Claude Code