Move to GitHub OAuth from bare GitHub username entry
- Dominant language
- Kotlin
- Stars
- 15
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
- As of now, we only enter the GitHub username to ping the GitHub API and that sends back a basic JSON response that we parse to provide a small and simple profile.
- But for different usecases like viewing repositories and the names of followers GitHub only sends back the first 30 results, which is not useful.
- Authenticate via GitHub OAuth since that is required for production apps.
Contributor guide
Research direction
The issue names no files or tests. Review the GitHub username/API profile flow and merged pull request #76 first, then compare its OAuth coverage with the repository and follower use cases described. Done means the app authenticates through GitHub OAuth rather than bare username entry for the production use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, kotlin
- Domain
- api, authentication, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 18/100