Contributors UI shows incorrect count (4 instead of 2) despite API returning correct data

[Marcel-Bich]

Select Topic Area

Bug

Body

Bug Description

The contributors page for my repository displays 4 contributors in the GitHub UI, but the GitHub API correctly returns only 2 contributors. This appears to be a UI caching issue that persists despite clearing the repository history.

Repository

https://github.com/Marcel-Bich/dogma

Expected Behavior

The GitHub UI should display 2 contributors matching the API response:

• Marcel-Bich (110 contributions)
• github-actions[bot] (1 contribution)

Actual Behavior

The GitHub UI displays 4 contributors (incorrect count)

Evidence

API Response (Correct)

curl -s https://api.github.com/repos/Marcel-Bich/dogma/contributors?per_page=100 | jq '.[] | {login,contributions}'

Result:

{
  "login": "Marcel-Bich",
  "contributions": 110
}
{
  "login": "github-actions[bot]",
  "contributions": 1
}

Stats API Response

curl -s https://api.github.com/repos/Marcel-Bich/dogma/stats/contributors | jq '.'

Result:

{}

(Empty object, likely being recomputed)

Local Git History

git log --all --format='%aN' | sort -u

Only shows 2 authors:

• Marcel Bich
• github-actions[bot]

Steps Already Taken

1. ✅ Verified local git history - only 2 authors
2. ✅ Checked GitHub API - correctly returns 2 contributors
3. ✅ Force-pushed with rewritten history
4. ✅ Verified no old branches/tags with other authors exist
5. ✅ Tested in multiple browsers and devices - issue persists
6. ✅ Waited for cache expiration - no change

Environment

• Issue persists across multiple browsers (Chrome, Firefox, Safari)
• Issue persists across different devices and networks
• Issue has been present for several days

Conclusion

This appears to be a GitHub UI caching bug where contributor data is not being properly refreshed after repository history changes. The API endpoints show correct data, but the web interface displays stale information.

Impact

This creates confusion about repository authorship and contribution history, potentially affecting repository credibility and contributor recognition.

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