chore: script to update the repo stars in real time

[danielmarv]

Description

This pull request updates the process for synchronizing repository star statistics by replacing the manual file copy with an automated script that fetches live data from the GitHub API, and updates the cached data accordingly. It also updates the actual repository star counts in the repository_stats.json file.

Repository statistics automation:

• Replaces the previous file-copy approach in sync-repo-stats.mjs with an async script that fetches current star counts for a predefined list of repositories directly from the GitHub API, including support for authentication and rate limiting. If the API fetch fails, the script falls back to cached data or writes empty stats if no cache is available. The script writes the updated stats to repository_stats.json and logs the total star count.

Data updates:

• Updates the star counts for multiple repositories in repository_stats.json to reflect the latest values.

Changes Made

• Added...
• Modified...
• Fixed...

Related Issues

Screenshots (if applicable)

Checklist

• Tests added/updated
• Documentation updated
• Linting passes
• Branch up-to-date with main

Deployment Notes

[Copilot]

Pull request overview

This PR replaces the Next.js repo-stats synchronization step with a script that fetches current stargazer counts from the GitHub REST API, writing results into the cached nextjs/data/repository_stats.json used by the site.

Changes:

• Reworked nextjs/scripts/sync-repo-stats.mjs to fetch stars from GitHub (optionally authenticated) with fallback to cached data.
• Updated nextjs/data/repository_stats.json with refreshed star counts.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
nextjs/scripts/sync-repo-stats.mjs	Replaces file-copy sync with GitHub API fetch + cache fallback and output writing.
nextjs/data/repository_stats.json	Refreshes cached star counts consumed by the Next.js UI.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

run() recomputes totalStars with Object.values(stats).reduce((sum, r) => sum + r.stars, 0), which will produce NaN or throw if any cached entry is missing/null/has non-numeric stars (possible when falling back to a partially-written or malformed cache). Reuse the existing totalStars(stats) helper here (and avoid naming the local variable the same as the helper) to keep the total robust.

Suggested change

	const totalStars = Object.values(stats).reduce((sum, r) => sum + r.stars, 0);
	console.log(`[sync-repo-stats] Done. Total stars: ${totalStars.toLocaleString()}`);
	const totalStarsCount = totalStars(stats);
	console.log(`[sync-repo-stats] Done. Total stars: ${totalStarsCount.toLocaleString()}`);

[Copilot]

This script runs during pnpm dev and pnpm build (via sync:repo-stats) and always makes 20 GitHub API calls. Without GITHUB_TOKEN, the unauthenticated limit (60 req/hr per IP) can be exhausted quickly in CI or during local development, causing frequent fallbacks/zeros. Consider adding a cache TTL / "only refresh when explicitly requested" behavior (e.g., skip the API fetch if a recent repository_stats.json exists, or require a token/flag to refresh).

[Copilot]

The hardcoded repos list is duplicated elsewhere in the repo (e.g., scripts/fetch-repo-stats.mjs). Maintaining multiple sources of truth increases the chance the Hugo and Next.js builds drift (different repo sets / missing new repos). Consider centralizing the repo list (single JSON/config module) and importing it from both scripts.