CodeForPhilly / CodeForPhilly/codeforphilly-ng
ops: publish codeforphilly-data-snapshot public repo (referenced in architecture.md but doesn't exist)
- 主要语言
- TypeScript
- 星标
- 1
- 派生
- 1
- 平均合并
- 5 天 3 小时
- 30 天内合并 PR
- 9
描述
## 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.
贡献指南
这个仓库没有索引到贡献指南
调研方向
从 apps/api/scripts/scrub-data.ts 开始,并阅读 specs/architecture.md 和 specs/behaviors/storage.md 中的引用。创建公开 repository CodeForPhilly/codeforphilly-data-snapshot,运行 scrubber 并 push 其结果,然后在 .github/workflows/ 下添加一个定时 workflow。当 snapshot 公开、完成初始填充,并使用 snapshot tag 每周刷新时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github-actions, typescript
- 领域
- data, devops
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 52/100