Stale contributor-list cache after history rewrite — BaranziniLab/biorouter

[Broccolito]

🏷️ Discussion Type

Bug

Body

GitHub Support ticket #4575471 was automatically closed and directed me to GitHub Community.

Repository

https://github.com/BaranziniLab/biorouter

Problem

The repository homepage's server-rendered deferred contributor fragment still reports Contributors 2 and lists github.com/claude:

https://github.com/BaranziniLab/biorouter/contributors_list?current_repository=biorouter&deferred=true

The repository history was rewritten on July 15, 2026, removing all 58 Claude Co-Authored-By trailers. The complete published default-branch history contains no Claude author, committer, or co-author attribution. Current main:

78f112aecb8cb7fd429827d17816d48994ea0db7

Clean API evidence

• https://api.github.com/repos/BaranziniLab/biorouter/contributors?anon=true&per_page=100 returns only Broccolito.
• https://api.github.com/repos/BaranziniLab/biorouter/stats/contributors returns only Broccolito.
• Multiple subsequent Broccolito-only commits were pushed after the rewrite.

The mismatch persisted beyond 24 hours. Clearing browser caches cannot resolve it because the fragment returned by GitHub itself is stale.

I found related reports, including #202032, #201982, and #200957.

Request

Could a GitHub staff member please escalate this for invalidation and recomputation of the server-side contributor-list/sidebar cache for BaranziniLab/biorouter?

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

[v-ember]

Hi @Broccolito,

This community is managed by GitHub employees, but it is not a support forum. The only place to go for answers to account-specific questions like this one is opening a ticket on our Support page.

This is a public forum, and the community is unable to assist with nor escalate your ticket, but we can assure you it is in the right place. There are an extremely high volume of Support tickets right now, yours will be answered in the order it was received based on the amount of tickets ahead of yours. Please open only one ticket per request.

As no other Community Discussions team members will be able to provide additional help with account related questions I am going to close this discussion. We appreciate your understanding and patience while Support works through your request!