Repository homepage Contributors sidebar remains at 76 after history cleanup; both REST endpoints return 1 contributor

[anyang1991]

Repository: https://github.com/anyang1991/anyang1991.github.io

The repository has been detached from its former fork and now has an independent default-branch history. GitHub reports fork=false and default_branch=master. After more than 24 hours, the homepage Contributors sidebar still lists contributors from the former template history.

Current evidence (2026-11-01):

• https://github.com/anyang1991/anyang1991.github.io/_sidebar returns contributors.contributorCount=76 and old template authors.
• https://api.github.com/repos/anyang1991/anyang1991.github.io/contributors?per_page=100&anon=true returns only anyang1991, with 12 contributions.
• https://api.github.com/repos/anyang1991/anyang1991.github.io/stats/contributors returns only anyang1991, with a total of 12 commits.
• The incorrect sidebar is reproducible in an incognito session.
• A subsequent normal code commit and push changed the commit count to 12 without refreshing the sidebar.
• Current HEAD: 509fc10d53d9a8ca993e4d66452471c124482b0d.

The documentation says contributor data can take approximately 24 hours to refresh after history changes, and recommends contacting Support if it remains stale. Support initially closed my report because this account is offered self-service resources and directed me to Community Discussions. The ticket was reopened with these details but has no further response yet.

Documentation: https://docs.github.com/en/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors#contributor-data-is-stale-after-history-changes

Is there a supported repository-owner operation to refresh the homepage contributors index specifically? If this requires GitHub-side maintenance, could a maintainer route this reproducible data inconsistency to the appropriate team? The contributor statistics already match the reachable history, so I am looking for a remedy for the homepage sidebar rather than another history rewrite.

[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.