Contributors graph still shows a stale entry days after a force-push removed it from history

[redyapr]

🏷️ Discussion Type

Bug

Body

Repo: https://github.com/redyapr/trefozeri

The Contributors graph (/redyapr/trefozeri/graphs/contributors, and the matching sidebar widget on the repo homepage) still lists a user as a contributor that hasn't had any commits in the repo's actual history for several days now.

What happened:

• A few commits originally had a Co-Authored-By: <name> <email> trailer whose email matched a verified email on that account.
• Those commits were removed from history via a force-push (rewritten, not just reverted).
• git log --all today — across every branch, including all open Dependabot branches — shows zero commits with that trailer, and zero commits authored/committed with that account's email, anywhere.
• The plain REST API (https://api.github.com/repos/redyapr/trefozeri/contributors) already reflects the correct state — only the actual two contributors are listed there.

So the underlying repo data is clean; only the Contributors graph (a separately cached/computed stat, distinct from the plain contributors API) is still stale. It's been several days — past the ~24h refresh window mentioned in the Viewing a project's contributors docs.

I opened a support ticket (personal/free tier) and it was closed as out-of-scope for direct support, pointed here instead. Has anyone dealt with a stuck/stale Contributors graph like this before? Is there a way to trigger a recompute myself, or is this just something that resolves eventually with more repo activity?

Happy to share exact commit SHAs (before/after the rewrite) if that's useful for anyone looking into it.

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