ci: replace cross-workflow dispatch with three self-contained workflows#76
Merged
Conversation
GITHUB_TOKEN cannot trigger workflow_dispatch events on other workflows (GitHub security restriction, regardless of actions:write permission). New structure — no cross-dispatch, each workflow is fully self-contained: - update-weekly.yml: scheduled Monday 06:00 UTC; runs full data fetch + chart generation in sequence; commits data/ + charts/ in one PR - update-data.yml: manual only; data fetch + DB assembly; commits data/ - update-charts.yml: manual only; downloads DB from GCS, regenerates dashboard charts; commits charts/ Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
Problem
GITHUB_TOKENcannot triggerworkflow_dispatchevents on other workflows — a hard GitHub security restriction regardless ofactions: writepermission. This caused the weekly data run to fail with HTTP 403 when trying to dispatchupdate-charts.yml.Solution
Three fully self-contained workflows — no cross-dispatch:
update-weekly.yml)update-data.yml)docs/data/update-charts.yml)docs/_includes/charts/Note: lobbying pipeline scripts (
get_MA_lobbying.pyetc.) are omitted from the weekly workflow here — they will be added whenfeat/ma-lobbying-datais merged.🤖 Generated with Claude Code