BIDHUB Contributors sidebar shows 4 while Insights and API show 3 #213418
Replies: 4 comments
|
💬 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. ⭐ |
|
@Giabao2110 you should try this #https://github.com/orgs/community/discussions/209302#discussioncomment-18705864, it worked for me. (the comment said to rename the default branch and then rename it back to the original version) |
|
Hey! This usually comes down to two things: First, check if someone pushed a commit using a local git email that isn't linked to their GitHub account. The sidebar counts unique commit authors from the git history, whereas Insights and the API only count actual registered GitHub users. You can check this locally by running Second, it could just be a caching delay. The sidebar and the Insights tab update on different schedules, so if history was recently rebased or a commit was removed, it might just take a few hours (up to a day) for the sidebar count to catch up. |
|
The two numbers are counting different things, so they don't have to agree. The REST Fastest way to see what's really in there: git shortlog -sne --all
git log --all --format='%an <%ae>' | sort -uIf you spot an email that belongs to a real account, adding it under that account's Emails settings will merge the identity. If it's a machine account or a The other half is staleness. GitHub documents that contributor displays can take about 24 hours to refresh after a force-push or history rewrite. Your last push was 13 November, so if history was touched around then you may just be inside that window. Renaming the default branch to something else and back is a known cache-buster that someone already suggested above, and it does often work — but it's worth waiting out the 24 hours first so you know whether you're fixing a cache or an identity. If it's still wrong after that, Support is the only one who can recompute the graph server-side. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
Body
On the BIDHUB repository Code page, the Contributors sidebar shows 4. The Insights Contributors view and the REST contributors endpoint both show 3. The current default branch is
mainat260053b.Could a GitHub staff member investigate and refresh the Code page Contributors list so it matches Insights and the API? Thank you.
All reactions