Contributions graph not counting older commits after adding (and re-adding) a verified email

[alpeykov]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

What I expected: older commits in my public repository to appear on my contributions graph once the commit email was added to my account.

What happens: only commits pushed after adding the email are counted; the older ones are still missing.

Details

• Repository: https://github.com/alpeykov/gas-consumption (public, not a fork)
• All commits are on the default branch (main) and use the same email address.
• On November 5, 2026 I added that address to my account as a secondary email and verified it. The commit pages and the API now attribute every commit to alpeykov.
• A commit pushed on November 6 shows on the graph right away.
• The older ones still don't, well over 24 hours later. For example, October 17 shows 1 contribution (about 49 commits that day), October 22 shows 3 (about 24), November 4 shows 0 (10).
• Today I removed the email, added it again and re-verified it to trigger a rebuild. No change so far.

I opened a support ticket (#4961292), but it was closed automatically because my plan doesn't include technical support.

Is there anything else I can do to trigger a recalculation of the contributions graph, or could someone from GitHub flag this for a rebuild?

Thanks!

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