Move GitHub contributors fetching to scheduled data-layer task

[pettinarip]

Summary

• Replace per-request GitHub API calls with pre-fetched data stored in Netlify Blobs
• Add fetchGitHubContributors scheduled task running weekly to fetch all contributor data
• Use git/trees API for single-request content file listing (replaces recursive directory walks)
• Fetch commits in parallel batches (20 concurrent requests) for performance
• Update contributors.ts to read from data-layer instead of making live API calls
• Bump @trigger.dev/sdk to 4.3.3

Test plan

• Verify the scheduled task runs successfully and stores data in Netlify Blobs
• Verify contributor information displays correctly on content pages
• Verify contributor information displays correctly on app pages
• Verify build succeeds without errors

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	4a897cf
🔍 Latest deploy log	https://app.netlify.com/projects/ethereumorg/deploys/69b2c3e32444ed0008cad38e
😎 Deploy Preview	https://deploy-preview-17174.ethereum.it
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 55 (🟢 up 2 from production) Accessibility: 94 (🟢 up 1 from production) Best Practices: 100 (no change from production) SEO: 99 (no change from production) PWA: 59 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[myelinated-wackerow]

Solid PR -- the architecture follows the established data-layer pattern cleanly, the tree API discovery is smart (single call vs recursive walks), and the parallel batching with rate limit handling is well done. The mechanical removal of the useless per-render commitHistoryCache across ~38 pages is correct and consistent.

A few notes:

1. Hardcoded date in exchangesByCountry.ts

The new exchangesByCountryLastUpdated export replaces a dynamic git log call, but it means anyone updating exchangesByCountry.ts needs to manually update this date too. Without an automated mechanism (pre-commit hook, script, etc.), this will inevitably drift. Worth at least a prominent comment warning maintainers, or better, an automated solution.

2. new Date().toISOString() fallback in contributors.ts

const lastUpdatedDate = gitHubContributors[0]?.date || new Date().toISOString()

If a slug is missing from the data-layer (new content added between weekly runs, data fetch failure, etc.), this shows "today" as the last edit date, which is misleading. The old code fell back to a local git log query which at least returned an accurate date. Consider a safer fallback -- perhaps a fixed epoch date, or omitting the date entirely when unknown.

3. Minor: JSDoc says "daily" but schedule is weekly

The fetchGitHubContributors JSDoc comment says "runs as a scheduled task (daily)" but it's registered in the WEEKLY array with a Sunday cron. Not a blocker, just a docs inconsistency.

---

Reviewed by Claude Opus 4.6

[pettinarip]

@wackerow thanks for the review! all three items addressed.

new Date().toISOString() fallback — now it hides the date entirely when contributor data is missing. lastEditLocaleTimestamp is optional throughout the type chain and the UI conditionally renders it. Showing any fallback date felt misleading regardless of source.

Additionally, investigating the missing dates uncovered a deeper bug: commits authored with emails not linked to a GitHub account return author: null from the API. The fetcher was filtering these out entirely, so pages with only such commits (e.g. community/support/faq) had no contributor data at all. Fixed by falling back to the git commit author name when the GitHub author is null.