feat(activity): add GitHub Discussions to RecentActivity

[Ridanshi]

Closes #1913

Implementation summary

The GitHub REST /user/events endpoint does not reliably surface DiscussionEvent and DiscussionCommentEvent entries — they are absent from the events feed for many users even when they have active discussion participation. This PR adds a parallel GraphQL query to fill that gap without replacing the existing REST event flow.

GraphQL integration details

A new DISCUSSION_COMMENTS_QUERY targets viewer.repositoryDiscussionComments(first: 20), the most reliable GitHub GraphQL field for this purpose. The query returns the 20 most recent discussion comments the authenticated user has made across all repositories, each with createdAt, comment url, and the parent discussion's title, number, url, and repository.nameWithOwner.

fetchDiscussionItemsViaGraphQL(token) wraps the call and always resolves — any error (rate limit, missing scope, disabled discussions) silently returns [] so discussion activity is never a hard dependency of the feed.

The GraphQL fetch runs in parallel with the REST events fetch via Promise.all in both fetchFormattedActivity() and the fetchPublicEvents fallback path.

Activity normalization changes

src/lib/activity-formatter.ts additions:

• GraphQLDiscussionCommentNode — typed shape for a single GraphQL response node
• formatGraphQLDiscussionComment(node) — normalizes a GraphQL node into the shared ActivityItem format; sets type: "discussion", builds the title as Commented on discussion #N, and links to the discussion URL (not the comment anchor)
• mergeActivityItems(restItems, discussionItems) — deduplicates by type-repo-createdAt-title key and returns a newest-first sorted array

src/app/api/metrics/activity/route.ts changes:

• Imports githubGraphQL from @/lib/github-fetch
• Adds DISCUSSION_COMMENTS_QUERY, DiscussionCommentsQueryResult, fetchDiscussionItemsViaGraphQL
• Both fetchFormattedActivity and the fallback path use mergeActivityItems to combine REST and GraphQL results

UI updates

None required. RecentActivity.tsx already renders the "discussion" type with a chat-bubble SVG icon and a "Discussion" badge — the existing code handles discussion items from both REST and GraphQL sources identically.

Tests added

test/activity-formatter.test.ts — 15 new tests (33 total):

formatGraphQLDiscussionComment:

• type is "discussion"
• title includes discussion number
• subtitle is discussion title
• repo is repository.nameWithOwner
• URL links to discussion (not comment anchor)
• createdAt is preserved
• id includes "gql-disc" and the comment URL
• handles different discussion numbers

mergeActivityItems:

• REST items sorted newest-first with empty discussion array
• Interleaves discussion and REST items chronologically
• Deduplicates items sharing the same type/repo/createdAt/title key
• Keeps distinct items differing only by title
• Returns only REST items when discussion array is empty
• Returns only discussion items when REST array is empty
• Returns empty array when both inputs are empty

Verification

npm run lint        # warnings only, no errors
npm run type-check  # no errors in changed files
npm run test test/activity-formatter.test.ts  # 33/33 passed

[vercel]

@Ridanshi 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]

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

[github-actions]

🎉 Merged! Thanks for contributing to DevTrack.

If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers.

Keep an eye on open issues for your next contribution!