Sidebar contributor list shows cached contributor though Insights graph is clean #208456
🏷️ Discussion TypeBug BodyHi GitHub Community, I am facing an issue where a removed contributor ("claude") is still showing on my repository's homepage sidebar (Contributors section shows 4 contributors), even though the git history has been cleaned up and the Insights > Contributors graph is completely updated and clean.
The two unreachable/orphaned commits were:
Both show the warning: "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository." Could GitHub staff or a moderator please advise on how to invalidate/refresh the homepage sidebar contributor cache, or trigger a repository cache rebuild so the sidebar matches the Insights graph? Thank you! |
Replies: 2 comments 1 reply
|
💬 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. ⭐ |
|
This happens because GitHub uses two different data sources for contributor information:
Furthermore, orphaned commits like To force GitHub to recalculate and rebuild the homepage sidebar contributor list immediately without waiting for background garbage collection: Option 1: Toggle the default branch (most reliable method)This forces GitHub's repository service to purge and recompute all default branch metadata:
Switching the default branch immediately purges the cached contributor widget and re-indexes only the commits reachable from Option 2: Push an empty commit to
|
This happens because GitHub uses two different data sources for contributor information:
/repos/somuai/somuai/contributors): These query the commit graph reachable from the default branch dynamically. Since your commits were rewritten and the branch deleted, this view is already accurate.Furthermore, orphaned commits like
f80faccandd7f6f5aare kept in Gi…