Skip to content

πŸ“Š Refresh CIA data (0 CSVs + production stats) - #3535

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
data/cia-csv-refresh
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
data/cia-csv-refresh

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

πŸ“Š Automated CIA data refresh

Pulled the latest service.data.impl/sample-data/ CSVs from
Hack23/cia@master
(resolved to commit f0d47a30b8e0c89bee4de1dbda86b140e3759763)
and re-ran the production-statistics pipeline against the same commit.

CSV refresh

Metric Count
Total tracked CSVs 146
βœ… Updated 0
🟰 Unchanged 140
❔ Missing upstream 0
⏭ Skipped (local-only) 6
❌ Failed downloads 0

Production statistics

  • Total persons: 2500
  • Total votes: 3793281
  • Last extraction: 2026-08-30 00:21:37.498449

How resolution works

The workflow never introduces new files β€” it only refreshes CSVs
already tracked under data/cia/** and cia-data/**. Upstream paths
are resolved through a recursive basename β†’ upstream-path index
built from the GitHub Tree API, so files living in
sub-folders (distinct_values/, framework-validation/,
risk-rule-tests/) are located correctly even though local paths
are organised differently. An <stem>_sample.csv alias is applied
for the handful of locally-renamed canonical files.

Review checklist

  • CSV diffs look reasonable (no schema regressions)
  • production-stats.json counts move monotonically or within reason
  • Dashboards still render with the refreshed data
  • No unexpected file additions or removals

Generated by .github/workflows/update-cia-csv-data.yml.

…0d47a3

- Upstream ref: master (resolved to f0d47a30b8e0c89bee4de1dbda86b140e3759763)
- CSV files: updated 0 / 146 tracked
- Production stats: 2500 persons, 3793281 votes
- Last extraction: 2026-08-30 00:21:37.498449
@github-actions
github-actions Bot force-pushed the data/cia-csv-refresh branch from 60238c7 to 2c57579 Compare October 28, 2026 03:36

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant