Contribution graph shows inconsistent counts when switching between years

[ubvc04]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

I noticed a possible issue with the contribution graph on my GitHub profile and wanted to check whether anyone else has experienced the same behavior.

Steps to reproduce:

1. Open my GitHub profile.
2. Observe the contribution count for the current year.
3. Switch to the previous year in the contribution graph.
4. Switch back to the current year.

Observed behavior:

• On initial page load, the current year shows 127 contributions.
• After switching to the previous year, it shows 227 contributions.
• When switching back to the current year, the contribution count changes to 68.

Expected behavior:

• The contribution count for a selected year should remain consistent and should not change when switching between years.

Additional information:

• The difference is 59 contributions (127 → 68).
• I reproduced this issue multiple times.
• The issue occurs on two different laptops.
• The issue also occurs in incognito/private browsing mode.
• Hard refresh does not resolve the issue.
• I recently restored approximately 50 repositories before noticing this behavior, although I am not sure whether that is related.

Has anyone else experienced a similar issue with contribution counts or the contribution graph?

Thank you.

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

[4Raisan]

Before treating 127 → 68 as lost contributions, compare the actual date ranges displayed in both views. The initial profile graph is described as contributions “in the last year,” which is not necessarily the same period as selecting the current calendar year. GitHub documents the initial view here: https://docs.github.com/en/account-and-profile/how-tos/contribution-settings/viewing-contributions-on-your-profile

If the first view includes late-2025 dates and the selected 2026 view begins in January, contributions from that late-2025 portion could explain the difference. This is a hypothesis to check against the graph labels, not a conclusion that your restored repositories caused it.

If both views really cover identical dates, capture the heading, first/last dates, selected year and URL before and after the switch. Compare several individual days’ tooltips as well as the total. That distinguishes a different reporting period from the same period returning inconsistent data and makes a much stronger bug report. Don’t delete or restore repositories again just to try to repair the count.

[ubvc04]

Thanks I got to know