concourse / concourse/github-release-resource
Check fails for repos with a lot of releases
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 57
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Using the github-release-resource with repositories that contain more then 1000 releases, the check step fails with
422 Only the first 1000 results are available.
Reproduction steps
Use the resource with a repo with more then 1000 releases
Expected behavior
The resource does not list every possible release, or stops after 1000
Additional context
It looks like this was introduced with #96
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 by reproducing the check step with a repository containing more than 1000 releases, then trace the release-listing request used by the resource. Done means the check no longer fails with GitHub's 422 response and stops or limits release results as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100