Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Community metrics can silently go stale: updatedAt is never rendered and a failed fetch keeps old numbers

Geschlossen
  • Stimmt etwas nicht?
#327 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

@IanoNjuguna arbeitet bereits daran.

Seit 14.10.2026.

  • #330 von @IanoNjuguna — offen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

enhancement

Problem

website/src/data/githubData.json drives the homepage community metrics. It is regenerated at build time by scripts/fetch-github-data.js (npm prebuild), and two things make it impossible to tell fresh data from months-old data:

  1. A failed fetch keeps the old numbers. The script reads the existing file first and preserves contributors and stats; if the API call then fails, it writes the preserved values back and only refreshes updatedAt. The payload is written unconditionally at the end.
  2. Nothing renders updatedAt. grep -rn "updatedAt" website/src returns no matches. Contributors.tsx:12 reads contributors; MonthlyPulse.tsx:7-9 reads stats. The timestamp is written, committed, and then never shown.

Evidence (2026-10-14)

  • Committed snapshot: updatedAt 2026-08-01, mergedPRs 136 / openIssues 12 / closedIssues 56.
  • A fetch run today: 162 / 9 / 77.

Those two states render identically to a visitor. If a fetch fails — rate limiting on an unauthenticated build (local builds here inject 0 env vars, no GITHUB_TOKEN), network hiccup, expired token — the site ships the older numbers with no marker.

Impact

  • Visitors cannot judge how current the metrics are.
  • Maintainers have no signal that a build silently fell back to a previous snapshot; the site keeps looking healthy.
  • The snapshot in the repo is already ~10 weeks old, so the fallback path is a real, not theoretical, state.

Suggested fix

Either or both:

  • Render updatedAt in MonthlyPulse as a "data as of …" line.
  • Fail (or warn loudly in the build log) when the fetch falls back to the previous snapshot, or when updatedAt is older than a threshold such as 7 days.

Notes

Independent of the font-loading work in #325. Raised while auditing what writes githubData.json, since npm run build / npm start rewrite that file on every run.

Related: #326 — the same fetch script can render automation accounts as contributors.

Vorherrschende Sprache
TypeScript
Sterne
13
Forks
22
Ø Merge
3 T. 2 Std.
Gemergte PRs (30 T.)
14

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus IntersectMBO/developer-experience

Alle Issues in IntersectMBO/developer-experience

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.