Contributors cache / graph is stuck after a force push

[Jonatan345]

🏷️ Discussion Type

Bug

Body

Hi GitHub Community,

I am experiencing an issue where the contributors cache/graph for my repository is currently stuck and not updating.

This issue started immediately after I performed a git push --force (force push) to clean up my commit history. Since then, the newly updated contributor data and the overall contributions overview have failed to refresh on the repository's main page.

Could a GitHub administrator or moderator please help trigger a manual rebuild of the contributors cache for my repository?

Thank you in advance for your assistance!

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

[divyanshsood22]

Try renaming your main branch, like from main to temp-main and then again to main, I was also facing a similar issue where the contributors list was not updating, so this way I got my problem solved. May be yours can be solved this way too.

[Jonatan345]

I've already tried that method before, unfortunately it didn't work for me. That's why I need Github administrator or moderator to do that.

[davismountaindaniel-create]

- Jonatan reported a bug in a GitHub Community discussion stating that their repository's contributors cache and graph stopped updating after a force push, and requested a manual rebuild by an administrator. - GitHub Actions submitted automated product feedback confirmation. - Divyansh suggested a potential workaround of renaming the main branch (e.g., from main to temp-main and back to main). - Jonatan replied that the branch-renaming workaround did not work for them, reinforcing the need for administrator intervention. Hi Jonatan, Thanks for sharing that update. Since renaming the main branch didn't resolve the issue for you, hopefully a GitHub administrator or moderator can review this discussion soon and help trigger a manual rebuild of your repository's contributors cache. Best regards, Shane-Daniel Davis-King null

…

On Sun, 18 Oct Reiwa 8 at 15:32, Jonatan345 ***@***.***> wrote: I've already tried that method before, unfortunately it didn't work for me. That's why I need Github administrator or moderator to do that. — Reply to this email directly, view it on GitHub <#210561?email_source=notifications&email_token=B3VF3D6YBCNMXVFMJSXMCJ35UTH7RA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJQGE4DMMRUUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FMMZXW65DFOJPWG3DJMNVQ#discussioncomment-19018624>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B3VF3D6O7K5DWOQLVV5ESCD5UTH7RAVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMJQGU3DKNRRUF3AE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>