Skip to content

feat(submit): add a seed command for the launch list - #60

Merged
jamesconwaydev merged 1 commit into
mainfrom
task-18-seed-cmd
Nov 6, 2026
Merged

jamesconwaydev merged 1 commit into
mainfrom
task-18-seed-cmd

Conversation

@jamesconwaydev

Copy link
Copy Markdown
Collaborator

Adds python -m scripts.submit seed --file seeds.csv --out report.json [--apply].

Each CSV row (repo,category,description, extra columns ignored) goes through the same repo and description checks as a submission, via a _check helper now shared with decide(). There's no trust check, rate limit or issue form. Passing rows become entries with submitted_by: jamesconwaydev, added_by_seed: true and issue: 0 (the schema and validate_data accept any integer, and no issue backs a seed).

  • Duplicates are checked against entries.json and against earlier rows in the same file.
  • GitHubError, RateLimited, Undecided and network errors mark a row undecided, never fail, and the run carries on.
  • The report is rewritten after each row. A re-run skips rows already decided and retries undecided ones, so a long rate-limit wait can be resumed.
  • --apply appends the passing entries through entries.save() and runs validate(), exiting 1 on errors.

Part of the v0.1 launch.

The launch list needs a few hundred repos put through the same repo and
description checks a submission gets, without the trust check, the
weekly limit or an issue form. `seed` reads a repo,category,description
CSV, writes a per-row ok/fail/undecided report, and with --apply adds
the passing rows to entries.json and validates it.

API errors mark a row undecided instead of failing it, so one bad repo
can't sink the run. The report is rewritten after every row and decided
rows are skipped on the next run, so a long rate-limit wait can be
resumed. Seed entries carry issue 0, since no issue backs them.
@jamesconwaydev
jamesconwaydev merged commit 428f767 into main Nov 6, 2026
9 checks passed
@jamesconwaydev
jamesconwaydev deleted the task-18-seed-cmd branch November 6, 2026 02:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant