chore: add batch issue generation script - #1
Merged
Merged
Conversation
Add scripts/generate-issues.sh, which upserts the repo's five labels and opens the initial backlog. The script is idempotent — labels use --force and issues are skipped when a matching title already exists — so it is safe to re-run. Each issue corresponds to a real, code-verified gap: a missing factory initialize event, unbounded treasury view reads, lifetime-only budget caps, and a read-after-write race in verify.sh. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
scripts/generate-issues.sh, which upserts the repo's five labels and opens the initial backlog.The script is idempotent — labels use
--forceand issues are skipped when a matching title already exists — so it is safe to re-run. Each issue corresponds to a real, code-verified gap in the shipped contracts:initializewrites storage but emits nothing, unlikedeploy_treasury(contracts/factory/src/lib.rs:48-57).get_categoriesandget_requests_by_categoryloop over all storage with no limit, while the factory already caps at 50 (contracts/treasury/src/lib.rs:499,:526).contracts/treasury/src/lib.rs:160).get_orgcan race the deploy's propagation (scripts/verify.sh:64-84).No contract logic changes; this only adds tooling.
🤖 Generated with Claude Code