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

I've confirmed this isn't a matter of leftover commits somewhere I missed — I ran git log --all --author=elahehshadkam on fresh clones of both repositories and got no results across any branch or tag, not just main. I also double-checked git ls-remote on both repos to make sure there are no stray refs still pointing at the old history.
Given that:
The filtered view (?author=elahehshadkam) correctly shows no commits
A full --all branch/tag search locally shows no commits
The history was rewritten and force-pushed more than 48 hours ago
...I'm fairly confident this isn't a propagation delay or a ref I've overlooked. It looks like the Contributors sidebar and the "committed in the past week" indicator are being served from a separate statistics cache that didn't get invalidated when the history was rewritten via force-push. That would explain why the live commit query is accurate but the sidebar isn't — they appear to be two different data sources under the hood.
Since GitHub Support directed me here because technical support isn't included in my plan, I'm hoping a staff member or moderator can help with one of the following:
Confirm whether contributor stats are expected to auto-refresh after a force-push, or whether this requires a manual rebuild on GitHub's end.
If a manual rebuild is needed, trigger that for these two repositories:
abdolhoseini/ai-voice-of-customer-analyzer
abdolhoseini/course-registration-email-automation
In the meantime, I'll try a couple of workarounds people have mentioned for stale contributor stats (toggling repo visibility, renaming the default branch and back) and report here if either one clears it — but since this seems to be a caching/indexing issue rather than something fixable from the repo settings, I'd really appreciate confirmation from GitHub staff either way.
Happy to provide any additional info (repo IDs, timestamps of the force-push, etc.) if that helps investigate.
Thanks again.