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 repository homepage has displayed "No contributors" since the fork was created, while the contributors graph and REST API contain contributor records. Could GitHub investigate the homepage sidebar's contributor data/index and repair or refresh it?

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 first day of this fork, and it remains reproducible on October 8, 2026 (Asia/Taipei). This predates the latest release and is not just a brief delay following that release.

Steps to reproduce

1. Open the affected repository homepage.
2. Inspect the Contributors section in the right sidebar: it displays "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 the repository's contributors instead of reporting that none exist.

Fresh diagnostic evidence

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

Endpoint	HTTP status	Result
https://github.com/Evanlau1798/codex-chatgpt-web/_sidebar	200	contributors.contributorCount = 0; contributors.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 actual homepage sidebar response contains:

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

GitHub request IDs for the same observation:

• Homepage sidebar: D414:28E90F:37357:56C7A:6AC6992E
• Contributors graph data: D415:2361D3:35A55:54925:6AC6992E

The homepage's current JavaScript reads the /_sidebar response and explicitly renders "No contributors" when contributorCount is zero. Thus the empty homepage matches the returned server data; it is not merely a loading skeleton. The sidebar 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. The contributor records already link to GitHub accounts, so the evidence does not suggest that all commit authors are unrecognized.

Contributor graph totals exclude merge/empty commits and can differ from the list API's totals; this report concerns the homepage returning zero, not those expected 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

A possibly related report describes the same homepage/detail-page discrepancy: https://github.com/orgs/community/discussions/190096. I cannot determine whether it shares the same internal cause.

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

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.