RealDevSquad / RealDevSquad/website-backend
Optimize PR #946, getting users based in github PR's
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Pr #946 To be optimized
currently while getting the PR details, all user's data is fetched for mapping PR and users data, which is not required.
We can get the GitHub user's names from PR details and using those we can get the user's details, this way we will be only reading users' data which are present in GitHub PR
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 with PR #946 and the linked diff around lines 76-79, where pull-request details are used to map GitHub users. Trace how user data is currently fetched and compare it with the names available in the PR details. Done means only users present in the GitHub PR are read while the existing mapping behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript, node.js
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100