Right now a maintainer reads an add-winner issue and hand-writes the YAML. That is the main bottleneck on data throughput.
Wanted: scripts/issue-to-yaml.ts that takes an issue number, reads the parsed issue-form fields via the GitHub API, and writes hackathon/project/entry YAML using the same helpers as scripts/add-winner.ts.
Requirements
- Never overwrite an existing file (mirror the behaviour in
add-winner.ts)
- Reuse an existing hackathon/project when the slug matches
- Warn on unknown category/technology slugs instead of inventing them
- Leave
verification.status for a human to confirm — the script must not self-certify a source
A follow-up could run it from a workflow on a maintainer command, but the script alone is the useful half.
Right now a maintainer reads an add-winner issue and hand-writes the YAML. That is the main bottleneck on data throughput.
Wanted:
scripts/issue-to-yaml.tsthat takes an issue number, reads the parsed issue-form fields via the GitHub API, and writes hackathon/project/entry YAML using the same helpers asscripts/add-winner.ts.Requirements
add-winner.ts)verification.statusfor a human to confirm — the script must not self-certify a sourceA follow-up could run it from a workflow on a maintainer command, but the script alone is the useful half.