Stale contributor attribution remains after rewriting repository history

[StevenYugsiU]

🏷️ Discussion Type

Bug

Body

Hello,

I rewrote and force-pushed all branches of this public repository:

https://github.com/StevenYugsiU/spectravisionwebapi

The goal was to remove this commit trailer:

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com

The current histories of these branches no longer contain references to Claude or Anthropic:

• main
• Steven
• Cristhian

I verified this with:

git log origin/main --format="%H%n%B%n---" | grep -iE "anthropic|co-authored-by: claude"
git log origin/Steven --format="%H%n%B%n---" | grep -iE "anthropic|co-authored-by: claude"
git log origin/Cristhian --format="%H%n%B%n---" | grep -iE "anthropic|co-authored-by: claude"

All commands return no results.

GitHub Insights > Contributors also does not list Claude.

However, the repository homepage still shows Claude in the contributor summary.

The repository still exposes these old pull request refs:

refs/pull/1/head -> 298ecc06deefd2bc01c78acee29180c8e6a0574a
refs/pull/2/head -> b2c7c7c41625f56f4aa540169e416b8b01784739

Is there any supported way to refresh the homepage contributor summary or remove stale contributor attribution associated with old pull request refs?

I have already:

• rewritten the commit history;
• force-pushed all active branches;
• verified that no current branch contains the old co-author trailer;
• run repository cleanup locally.

I am attaching a screenshot showing that Claude still appears only in the contributor summary on the repository homepage.

Thank you.

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