Skip to content

fix: resolve GitHub OAuth redirect failure#1334

Open
Shanidhya01 wants to merge 1 commit into
Priyanshu-byte-coder:mainfrom
Shanidhya01:fix/github-oauth-auth-bug
Open

fix: resolve GitHub OAuth redirect failure#1334
Shanidhya01 wants to merge 1 commit into
Priyanshu-byte-coder:mainfrom
Shanidhya01:fix/github-oauth-auth-bug

Conversation

@Shanidhya01
Copy link
Copy Markdown

Summary

Fixes the GitHub OAuth authentication issue where users were redirected back to the sign-in page with error=github instead of being successfully authenticated and taken to the dashboard.

Closes #1221

Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Refactor / code cleanup

Changes Made

  • Fixed GitHub OAuth authentication flow configuration
  • Corrected redirect/callback handling after successful login
  • Improved environment variable handling for production deployment
  • Added better error handling/logging for OAuth authentication failures
  • Verified compatibility between local and Vercel deployment environments

How to Test

Steps for the reviewer to verify this works:

  1. Run the application locally with valid GitHub OAuth credentials
  2. Navigate to the sign-in page
  3. Click Sign in with GitHub
  4. Complete GitHub authorization flow
  5. Confirm successful redirect to /dashboard
  6. Verify no redirect loop occurs with error=github
  7. Test deployed preview build to confirm production auth flow works

N/A (Authentication bug fix)

Checklist

  • Linked issue in summary
  • npm run lint passes locally
  • No TypeScript errors (npm run type-check)
  • Self-reviewed the diff
  • Added/updated tests if applicable

@vercel
Copy link
Copy Markdown

vercel Bot commented May 27, 2026

@Shanidhya01 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix type:security GSSoC type bonus: security (+20 pts) labels May 27, 2026
@github-actions
Copy link
Copy Markdown

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

  • level:beginner — 20 pts
  • level:intermediate — 35 pts
  • level:advanced — 55 pts
  • level:critical — 80 pts

Quality (optional):

  • quality:clean — ×1.2 multiplier
  • quality:exceptional — ×1.5 multiplier

Validation (required to score):

  • gssoc:approved — counts for points
  • gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

  • Make sure CI is passing (type-check + lint)
  • Double-check the PR description is filled out and the issue is linked
  • Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix type:security GSSoC type bonus: security (+20 pts)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] GitHub OAuth Error Redirect Loops Back to Sign-In Page

1 participant