Feature: GitHub Profile Info Integration

[Annanyatiwary4]

Description

Currently, when users add their GitHub username to their profile, the dashboard card only redirects them to their GitHub profile page. This enhancement will fetch their GitHub data and display it on a dedicated profile info page inside DevSync.

Frameworks / Libraries to Use: React, Tailwind CSS, ShadCN UI, Aceternity UI.

Workflow

1. User adds their GitHub username to profile.
2. Backend fetches GitHub user data from API.
3. Dashboard card updates → instead of redirecting to GitHub, it links to a new internal profile info page.
4. Profile info page displays the fetched GitHub data.

Tasks

Backend / API

• Implement endpoint to fetch GitHub user data (profile, repos, contributions).
• Fetch detailed stats using GitHub API:
  • Profile info (avatar, name, bio, followers, following).
  • Repository summary (top repos by stars/forks).
  • Contribution stats (commits, languages used).
  • Contribution streaks, active days, and activity heatmap.
• Add refresh logic to update data periodically or on-demand.

Frontend / Implementation

• Create a new GitHub Profile Info Page in the dashboard.
• Display fetched data in a visually structured way:
  • Profile Section: Avatar, name, bio, followers/following.
  • Repositories Section: Top repos by stars/forks with quick links.
  • Contributions Section: Commits, languages used, contribution streaks, active days visualization.
• Update GitHub card → redirect to internal profile info page instead of external link.
• Style with ShadCN UI, Aceternity UI, Tailwind CSS.

Testing

• Add GitHub username → verify info page displays correctly.
• Handle invalid usernames gracefully.
• Verify contribution streaks and activity display correctly.
• Test responsiveness across devices.

🎯 GSSoC 2025

• Level: 3 (10 Points)
• Estimated Completion Time: 3–4 days

General Contribution Guidelines

• Pull the latest changes from the main branch before raising a PR.
• PRs for unassigned issues will be rejected.
• Complete your current PR before claiming a new issue.
• Follow the project’s style and branding consistency.
• Ensure your work is reviewed before submitting a PR.

To Know More

• Please read the Contributing Guidelines.

[RAGHU1242]

@Annanyatiwary4 i want to work on this .Could you assign this issue to me

[AvaneeshKesavan]

I would like to work on this feature. Please assign it to me.

[github-actions]

🎉 Thank you @AvaneeshKesavan for picking up this issue!
Please make sure to follow our contributing guidelines here 👉 Contributing Guidelines
Happy coding !!
and Don't forget to give this repo a 🌟

[RAGHU1242]

@Annanyatiwary4 I want to work on this . And I have asked for first. Can you assign this to me

[AvaneeshKesavan]

When I try to run the backend locally, it crashes immediately with the following error:

TypeError: OAuth2Strategy requires a clientID option
at Strategy.OAuth2Strategy ...

It seems this is caused by the Google OAuth strategy in passport.js requiring GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET environment variables.

Because of this, the backend cannot start even if we are not using Google login

[Annanyatiwary4]

@AvaneeshKesavan
Please check the Docs section.
It contains proper steps on how to set up environment variables.
Follow the instructions, and if you still face any issues, let me know!!

[Annanyatiwary4]

@RAGHU1242 as your current issue has not been completed. That's why it's not assigned to you.
Please complete the existing task to get assigned new issues .