Contributors sidebar widget shows a stale contributor no longer in any commit #206846
Unanswered
GianMandara
asked this question in
Repositories
Replies: 1 comment
|
💬 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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
Body
Hi there,
The small "Contributors" widget on my repository's main page (top-right sidebar) is showing an outdated contributor who no longer appears in any commit's author or committer field.
Repository: https://github.com/GianMandara/Sistema-Professor-V2
What I checked:
git log --format="%an <%ae> | %cn <%ce>" for every commit in the repo shows only one author/committer across the entire history.
The full contributors graph (https://github.com/GianMandara/Sistema-Professor-V2/graphs/contributors) already correctly shows only one contributor.
I pushed an empty commit a few days ago specifically to try to force a stats recompute — it fixed the full graphs page, but the small sidebar widget on the repo's main page is still showing the stale second contributor.
This looks like the small sidebar widget is served from a separate cache than the full /graphs/contributors page, and that cache hasn't been invalidated.
Could someone help trigger a recompute of that specific cache, or let me know if this is expected to resolve on its own over time?
Thanks!
All reactions