Repository homepage shows No contributors since fork creation, but graph and API return 16 contributors

[Evanlau1798]

🏷️ Discussion Type

Bug

Body

The Contributors section on my public fork's homepage has displayed "No contributors" since the fork was created, although the contributors graph and REST API contain contributor records. Please investigate the homepage sidebar's contributor data/index.

Affected repository: https://github.com/Evanlau1798/codex-chatgpt-web
Owner: Evanlau1798
Parent repository: https://github.com/miuuyy/codex-chatgpt-web
Default branch: main
Fork creation timestamp (REST API): 2026-08-21T00:31:51Z

I have observed this since the fork's first day. It remains reproducible on October 8, 2026 (Asia/Taipei), so this is not just a brief delay following the latest release.

Steps to reproduce

1. Open the affected repository homepage.
2. Inspect Contributors in the right sidebar: it says No contributors.
3. Open https://github.com/Evanlau1798/codex-chatgpt-web/graphs/contributors or query the endpoints below: contributor records are available.

Expected behavior

The homepage should show contributors instead of reporting that none exist.

Diagnostic evidence

Requests at 2026-10-07 19:10:38 UTC (2026-10-08 03:10:38 Asia/Taipei):

Endpoint	HTTP	Result
https://github.com/Evanlau1798/codex-chatgpt-web/_sidebar	200	contributorCount = 0; contributors = []
https://github.com/Evanlau1798/codex-chatgpt-web/graphs/contributors-data	200	16 contributor records
GET /repos/Evanlau1798/codex-chatgpt-web/contributors?per_page=100	200	16 named contributors, including Evanlau1798 with 801 contributions
GET /repos/Evanlau1798/codex-chatgpt-web/stats/contributors	200	16 contributor records

The homepage sidebar response includes:

{"contributors":{"contributorCount":0,"contributors":[],"contributorsPath":"/Evanlau1798/codex-chatgpt-web/graphs/contributors"}}

GitHub request IDs:

• Sidebar: D414:28E90F:37357:56C7A:6AC6992E
• Graph data: D415:2361D3:35A55:54925:6AC6992E

The homepage JavaScript reads /_sidebar and renders "No contributors" when contributorCount is zero. The Contributors section is enabled. A control request to the parent repository's /_sidebar returned 11 contributors.

The repository has 1,296 reachable commits, below the 10,000-commit insights threshold. Contributor records already link to GitHub accounts. Graph totals exclude merge/empty commits and can differ from the list API; this report concerns the homepage returning zero, not expected total differences.

Reproduction commands

curl -sS -H 'Accept: application/json' -H 'X-Requested-With: XMLHttpRequest' https://github.com/Evanlau1798/codex-chatgpt-web/_sidebar
curl -sS -H 'Accept: application/json' -H 'X-Requested-With: XMLHttpRequest' https://github.com/Evanlau1798/codex-chatgpt-web/graphs/contributors-data
gh api 'repos/Evanlau1798/codex-chatgpt-web/contributors?per_page=100'
gh api repos/Evanlau1798/codex-chatgpt-web/stats/contributors

Possibly related report: https://github.com/orgs/community/discussions/190096 (I cannot confirm the same internal cause).

This is a resubmission of https://github.com/orgs/community/discussions/209774 through the official GitHub UI template, as requested by the automated closure notice.

Please investigate why the homepage remains empty despite populated graph/API data, and advise whether a repository-specific index refresh or other GitHub-side repair is required.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[will-lynas]

Seeing the same homepage symptom on https://github.com/NousResearch/hermes-agent, a public, non-fork repository. The sidebar previously showed contributors but now says “No contributors.”

Checked on 30 October 2026:

• GET /NousResearch/hermes-agent/_sidebar returns HTTP 200 with "contributorCount": 0 and "contributors": [].
• GET /repos/NousResearch/hermes-agent/contributors?per_page=5 on api.github.com returns HTTP 200 with contributor records, including @teknium1 and @kshitijk4poor.
• Unlike the original report, both /graphs/contributors-data and the REST /stats/contributors endpoint return []. The graph page says “We don't have enough data to generate this graph.”

This repository has approximately 60,830 commits, so the documented limitations above 10,000 commits may affect the graph. However, displaying “No contributors” on the homepage is misleading when the contributors API returns records.

Could GitHub investigate whether this is the same issue or a separate large-repository limitation?