📊 Refresh CIA data (0 CSVs + production stats)#3005
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
…01520d - Upstream ref: master (resolved to d01520d8ec89af2b20cf6c557b2f9af92ce64b91) - CSV files: updated 0 / 146 tracked - Production stats: 2499 persons, 3724917 votes - Last extraction: 2026-06-06 20:48:04.446826
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.
📊 Automated CIA data refresh
Pulled the latest
service.data.impl/sample-data/CSVs fromHack23/cia@master(resolved to commit
d01520d8ec89af2b20cf6c557b2f9af92ce64b91)and re-ran the production-statistics pipeline against the same commit.
CSV refresh
Production statistics
How resolution works
The workflow never introduces new files — it only refreshes CSVs
already tracked under
data/cia/**andcia-data/**. Upstream pathsare resolved through a recursive
basename → upstream-pathindexbuilt from the GitHub Tree API, so files living in
sub-folders (
distinct_values/,framework-validation/,risk-rule-tests/) are located correctly even though local pathsare organised differently. An
<stem>_sample.csvalias is appliedfor the handful of locally-renamed canonical files.
Review checklist
production-stats.jsoncounts move monotonically or within reason