Failed to login using github
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github
- Domain
- authentication
Research direction
Reproduce the login flow at http://gitly.org/ by selecting “Login via GitHub” and observe the GitHub 404 response from the linked OAuth authorization URL. Trace the login flow and OAuth configuration, then verify that GitHub sign-in completes successfully.
Written by the indexing model from the issue text.
Description
Steps to reproduce issue:
- Head to http://gitly.org/
- Click on sign in on top left trainer
- Click on Login via GitHub
- github returns 404.
- Dominant language
- V
- Stars
- 1.5k
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
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.
More from vlang/gitly
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oasisprotocol/oasis-sdk#2523 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
cost:cheap severity:medium
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fairagro/m4.2_sql_to_arc#227 ·