feat: wire DOCUSAURUS_GIT_TOKEN to GitHub service for live discussions

[Copilot]

The Discussions tab always rendered hardcoded mock data because githubService.getHeaders() checked window.GITHUB_TOKEN (never set at runtime), while the actual token was already available in customFields.gitToken (from DOCUSAURUS_GIT_TOKEN env var) — the same pattern statsProvider.tsx uses correctly for leaderboard data.

Changes Made

• githubService.ts — Added private token field + setToken(token: string) method; updated getHeaders() to prefer stored token, fall back to window.GITHUB_TOKEN
• dashboard/index.tsx — Added useDocusaurusContext to read customFields.gitToken; calls githubService.setToken() on mount; added a Refresh button (with spin animation) for manual re-fetch; error state now surfaces a direct link to GitHub Discussions when the API call fails
• discussions.css — Styles for .refresh-discussions-btn, @keyframes spin, and .spinning
• .env.example — Documented DOCUSAURUS_GIT_TOKEN with required scope (read:discussion)

// dashboard/index.tsx — token wiring
const { siteConfig: { customFields } } = useDocusaurusContext();
useEffect(() => {
  const token = customFields?.gitToken as string;
  if (token) githubService.setToken(token);
}, [customFields?.gitToken]);

When DOCUSAURUS_GIT_TOKEN is set in the deployment environment, the section fetches live discussions via GitHub GraphQL. Without a token, an error with a fallback link to the GitHub Discussions page is shown instead of silent mock data.

Dependencies

No new dependencies.

Checklist

• My code follows the style guidelines of this project.
• I have tested my changes across major browsers and devices
• My changes do not generate new console warnings or errors .
• I ran npm run build and attached screenshot(s) in this PR.
• This is already assigned Issue to me, not an unassigned issue.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
recode-website	Ready	Preview, Comment	Apr 22, 2026 6:13am

[Adez017]

so this will require updating the env with GIT_TOKEN along with the docusaurus one

[Adez017]

Hi @sanjay-kv could you look into the vercel deployment and let me know if things are working fine ?
ATM its looks good

[github-actions]

🎉 Your pull request has been successfully merged! 🎉 Thank you for your valuable contribution to our project.

I would be grateful if you can nominate for keeping this opensource project live and running Link to Nominate. Please do star the repo and Keep up the fantastic work! 🚀

[sanjay-kv]

@Adez017 it looks good in the preview.