Contributor statistics not updating after Git history rewrite #212340
🏷️ Discussion TypeBug BodyHi, I recently rewrote the Git history of my repository to remove unintended co-author attributions. Repository: https://github.com/Baggio94/slot-for-android I've verified all 144 commits on the default branch (
However, Claude still appears in the repository's Contributors section, despite no longer being present in the current Git history. I opened GitHub Support ticket #4967536, but it was automatically closed because my account only has access to self-service support. I found a similar case in [Discussion #205703](https://github.com/orgs/community/discussions/205703), where @ktravers manually refreshed the contributor statistics and resolved the issue. Could @ktravers or another GitHub staff member please manually refresh the contributor statistics for my repository? Thank you for your help! |
Replies: 2 comments 2 replies
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
the contributors list is cached, it doesn't get rebuilt from the current history automatically after a force push. a trick that worked for others without needing staff:
haven't tried it myself, but it's the usual workaround people report. if it doesn't change anything after a day, then it really needs staff to refresh it. |
the contributors list is cached, it doesn't get rebuilt from the current history automatically after a force push. a trick that worked for others without needing staff:
haven't tried it myself, but it's the usual workaround people report. if it doesn't change anything after a day, then it really needs staff to refresh it.