References #33.
/bounty $50
Summary
.github/workflows/seed-issues.yml creates the same starter issue list every time the manual workflow_dispatch job is run. It does not check whether an issue with the same title already exists, so repeated runs can duplicate the entire starter bounty queue.
Impact
Duplicate seeded issues make the bounty board noisy, split contributor attempts across multiple identical tasks, and create unnecessary review/triage work for maintainers.
Expected behavior
The seed workflow should be idempotent: if an open issue with the same starter title already exists, the workflow should skip creating another copy and continue with the rest of the list.
Acceptance criteria
- Before creating each starter issue, query existing open issues for the same title.
- Skip creation when an open issue with the same title already exists.
- Keep labels and issue body generation unchanged for issues that do need to be created.
- Keep the change scoped to the seed workflow and required AI-agent metadata.
- Include a short validation note explaining the duplicate-check path.
References #33.
/bounty $50
Summary
.github/workflows/seed-issues.ymlcreates the same starter issue list every time the manualworkflow_dispatchjob is run. It does not check whether an issue with the same title already exists, so repeated runs can duplicate the entire starter bounty queue.Impact
Duplicate seeded issues make the bounty board noisy, split contributor attempts across multiple identical tasks, and create unnecessary review/triage work for maintainers.
Expected behavior
The seed workflow should be idempotent: if an open issue with the same starter title already exists, the workflow should skip creating another copy and continue with the rest of the list.
Acceptance criteria