Contributors list still shows removed contributors after history rewrite

[VitorASC]

🏷️ Discussion Type

Bug

Body

Hello,

I rewrote the Git history of my repository and removed all commits from previous contributors.

Repository: https://github.com/VitorASC/GerenciamentoCarteira

Running:

git shortlog -sne origin/main

returns only:

"Personal info edited by staff"

There are no other remote branches containing the old history and there are no tags.

The history rewrite was completed several days ago, but the old contributors are still displayed in the Contributors section.

GitHub documentation says contributor statistics may take around 24 hours to refresh, but this has already exceeded that period.

I also contacted GitHub Support, but my ticket was closed because my account currently only has access to self-service support resources, and I was directed to GitHub Community Discussions.

Is there any way to force the contributor statistics to be recalculated, or is this something only GitHub staff can refresh internally?

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

[sm7313617-create]

Hey @VitorASC! I just checked your repo, the actual git history looks clean, just your commits are there. So the rewrite was fine, just the stats cache on Github being slow.

The fastest way to force a refresh is to push an empty commit .
That usually causes GitHub to recalculate nothing more than that. If it still does not update after a day or two, the only thing you can do is wait bro🥲 .... the backend that powers GitHub's contributor stats can take up to a week to fully resync after a force push, and repo owners don't get a manual refresh button.

I guess nothing broken on your side actually!

In case you need the commands for empty commits: 1. git commit --allow-empty -m "trigger stats refresh" then 2. git push