[FEAT] Add GitHub Discussions activity widget

[Priyanshu-byte-coder]

Summary

GitHub Discussions is increasingly used for community Q&A and proposals. DevTrack should surface discussion contributions alongside commits and PRs.

Expected Behaviour

A 'Discussions' section (or stat chips) showing:

• Discussions started this period
• Discussion comments/answers given
• Marked-as-answer count (a strong signal of community contribution)

Implementation Notes

• GitHub GraphQL: viewer.contributionsCollection has no discussion field yet
• Use REST: GET /search/issues?q=author:{user}+type:discussion (discussions appear in search)
• Or GitHub GraphQL: repository.discussions(filterBy: {createdBy: user})
• May require iterating over user's repos — cache aggressively

GSSoC Info

• Difficulty: Intermediate — 35 pts
• Area: Feature / Metrics

[himaparvathia23ec]

Hi @Priyanshu-byte-coder! 👋 I'd like to work on this issue.

Here's my plan:

• Use GitHub REST API GET /search/issues?q=author:{user}+type:discussion
  to fetch discussions started by the user
• Use GitHub GraphQL repository.discussions(filterBy: {createdBy: user})
  to get discussion comments and marked-as-answer count
• Build a DiscussionsWidget component in src/components/ showing
  3 stat chips:
  • Discussions started
  • Comments/answers given
  • Marked-as-answer count
• Add a new API route at src/app/api/metrics/discussions/
• Implement aggressive caching to handle repo iteration efficiently
• Follow strict TypeScript — no any types
• Run npm run lint and npm run type-check before submitting

I'd like to work on this — can you please assign it to me?

🌿 Branch Name
feat/258-github-discussions-activity-widget

💬 Commit Message
feat: add GitHub Discussions activity widget

[srinidhi-2006-bit]

Hi @Priyanshu-byte-coder

I’m also interested in contributing to this feature under GSSoC’26 if the issue becomes available later.

The Discussions activity tracking feature sounds very interesting, especially the integration of GitHub REST/GraphQL APIs for contribution metrics and caching strategies for efficient data fetching.

I’d be happy to help with implementation, UI integration, testing, or related improvements if needed.

Thank you!

[mallya-m]

Hi @Priyanshu-byte-coder!
Having already built the notification bell
(#411) and repo health panel (#306) for this project, I'm familiar with
the API route patterns here.

My approach for the Discussions widget:

• New GET /api/metrics/discussions route using GitHub GraphQL
  viewer.contributionsCollection — same pattern as the existing
  /api/metrics/prs route
• Three stat chips: discussions started, comments given,
  marked-as-answer count
• Aggressive response caching with Cache-Control headers to handle
  repo iteration without hitting rate limits
• New DiscussionsWidget.tsx component consistent with PRMetrics card style

Could you also assign this to me?
GitHub: github.com/mallya-m