Investigate GraphQL for PR extraction in release scripts
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Following up on the short-term fix in #37201, using the REST API (GET /repos/{owner}/{repo}/commits/{sha}/pulls) to fetch PRs per commit could lead to rate limits scaling issues under heavy merge commit volume.
We should investigate using the GraphQL API to batch associatedPullRequests for multiple commits at once to scale better. We could set this up as a parallel non-blocking path to compare results.
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 locating the release scripts and reviewing the short-term REST API fix in #37201. Compare the current per-commit pull request lookup with a GraphQL path using associatedPullRequests for multiple commits. Done means a non-blocking comparison path is set up and its scalability and result differences are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, graphql, java
- Domain
- api, performance, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100