ops: publish codeforphilly-data-snapshot public repo (referenced in architecture.md but doesn't exist)

Open
#115 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, typescript
Domain
data, devops

Research direction

Start with apps/api/scripts/scrub-data.ts and read the references in specs/architecture.md and specs/behaviors/storage.md. Create the CodeForPhilly/codeforphilly-data-snapshot public repository, run the scrubber and push its result, then add a scheduled workflow under .github/workflows/. Done means the snapshot is public, initially populated, and refreshed weekly with a snapshot tag.

Written by the indexing model from the issue text.

Description

What's missing

`specs/architecture.md` and `specs/behaviors/storage.md` both reference a public scrubbed snapshot of the data repo — `codeforphilly-data-snapshot` — that contributors can clone without needing access to the live production data. The snapshot is supposed to be produced by `apps/api/scripts/scrub-data.ts` and pushed periodically.

The scrubber script exists. The public snapshot repo does not.

Fix shape

Two pieces:

  1. One-time: create the `CodeForPhilly/codeforphilly-data-snapshot` public repo on GitHub; do the first `scrub-data` run; push the result.
  2. Recurring: add a scheduled CI workflow (GitHub Action on a weekly cron, say) that runs the scrub + force-pushes a fresh snapshot tag. Probably lives in `.github/workflows/` in this repo since the script lives here.

Why now

Pre-cutover-onboarding stories assume new contributors can clone the snapshot. If we leave the spec asserting the repo exists without it existing, new contributors hit a dead link.

Identified during the 2026-05-30 post-cutover-blog spec-drift audit.

Dominant language
TypeScript
Stars
1
Forks
1
Avg merge
1d 20h
Merged PRs (30d)
25

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeForPhilly/codeforphilly-ng

All issues in CodeForPhilly/codeforphilly-ng

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.