Investigate using GitHub user status for reviewer eligibility
Open
Nobody has claimed this yet.
backlog
feature
- Dominant language
- JavaScript
- Stars
- 210
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
as of 1/12/19, I don't yet see a way to get the user status using the v3 or GraphQL APIs, so will have to revisit this at a later time
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are identified. Start by checking the GitHub v3 and GraphQL API documentation for a user-status field, then inspect the repository's GitHub reviewer-eligibility entry point. Done means confirming whether the status is available and documenting a viable implementation path or the API limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100