Contributors sidebar still shows a removed co-author days after a force-push history rewrite

[cive202]

🏷️ Discussion Type

Bug

Body

I rewrote the commit history on my repo's main branch to strip a Co-Authored-By trailer from several commit messages (kept all the code/diffs identical, just edited the messages), then force-pushed the result to GitHub.

Repo: https://github.com/cive202/settleAI-NepaliVoiceAssistance

The rewrite is confirmed complete — filtering the Commits page by that author returns nothing:
https://github.com/cive202/settleAI-NepaliVoiceAssistance/commits/main/?author=claude
→ "No commits history"

I also checked every commit on every branch that exists on the remote directly via git log/git ls-remote — there's no commit anywhere in the current history with that author or co-author trailer.

However, the "Contributors" widget on the repo's main page (and /graphs/contributors) still lists that account as a contributor, more than 24 hours after the force-push — past the window GitHub's own docs give for contributor stats to refresh after a history rewrite.

I opened a support ticket about this and it was auto-closed as a self-service issue, so I'm posting here per that guidance.

Has anyone dealt with a contributor entry that survives a force-push rewrite? Is there a known way to force GitHub to recompute this (short of toggling repo visibility), or does this cache sometimes just take much longer than 24h to catch up?

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