Stale contributor sidebar after history rewrite (repository APIs are correct)

[WilliamDeklich]

🏷️ Discussion Type

Bug

Body

The homepage contributor sidebar for WilliamDeklich/exoplanet-transit-classifier remains stale nine days after a history rewrite.

On September 4, 2026, I rewrote the default branch to remove incorrect Co-Authored-By trailers and force-pushed the cleaned history. The current default branch is main, with HEAD:

58399045ef83040503fc040e6f3d59406d1753a1

The canonical repository data is clean:

• REST contributors lists only WilliamDeklich with 3 commits.
• Contributor statistics and Insights → Contributors show only WilliamDeklich.
• The repository has only the main branch, with no tags, pull requests, forks, or additional collaborators.
• All three commits reachable from main are authored and committed only by WilliamDeklich and contain no Claude/Anthropic co-author trailer.

However, the repository homepage still displays @claude under Contributors (2).

The old, now-unreferenced commit SHAs were:

• 62f503915527b3b06d55b4b539d7211f21edc447
• 33b16fcf0f4ca65d35ca6e498a72805149276b2d
• 4b092f6f6d82e4176a27866371fc4bfd0439c8b5

These old commits are on no branch, but their cached GitHub pages remain accessible by exact SHA. This appears to be a stuck repository-homepage contributor cache. A similar recent case was resolved by a GitHub staff member manually refreshing the list.

Could GitHub staff please manually refresh or invalidate the contributor list/sidebar cache for this repository?

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

[queenofcorgis]

Thank you for reporting this bug. We've been logging these posts and are currently investigating solutions. We will share updates as soon as work begins and we have a better sense of when it will ship.

In the meantime, we did publish a troubleshooting guide for folks who may have missing contributions if you haven't taken the steps outlined in this doc, I recommend doing those first.

We appreciate the patience!