project-robius / project-robius/makepad-packaging-action
Handle GitHub release assets with pagination
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Issue Content
- Problem: Asset listing uses single-page calls with per_page: 100 (src/index.ts:758, src/index.ts:769, src/index.ts:979).
- Impact: Repos with >100 assets may miss deletions/replacements and create inconsistent uploads.
- Proposed fix: Use octokit.paginate for all release asset reads.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in src/index.ts at lines 758, 769, and 979, where release assets are read with single-page calls. Replace the release asset reads with octokit.paginate and check that all three paths use pagination. Done means repositories with more than 100 release assets are fully considered for deletions and replacements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100