Verified commits missing from contribution graph after re-adding email: API attribution correct, daily counts zero

[shrutipanjwani]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

After re-adding and verifying a previously removed commit-author email, older contributions still appear to be missing from my profile.

My profile currently shows 492 contributions for the past year.

Profile: https://github.com/shrutipanjwani

Email re-added and verified: hello@shrutipanjwani.com
Time elapsed since verification: 24 hours

Eligible historical commits authored with the verified email should count toward my contribution graph.

I checked both local Git history and GitHub’s APIs:

• Commit patch headers contain the exact email verified on my account.
• GitHub’s API attributes three sampled commits to shrutipanjwani.
• The affected repository is private and is not a fork.
• Its default branch is main.
• GitHub’s compare API confirms all three sampled commits are ancestors of the current main.
• Their author and committer dates agree.

Despite this, GitHub’s contribution calendar reports:

Date	Verified commits on the default branch	Calendar contribution count
September 2, 2026	At least 1	0
September 7, 2026	At least 2	0

For November 14, 2025 through November 13, 2026, the GraphQL contribution calendar returns 492 total contributions, all reported as restricted contributions.

Separately, local history contains 336 commits on main from the past year using this verified email. I am not claiming all 336 are missing; the three API-verified examples above demonstrate the discrepancy.

Could GitHub staff investigate whether historical contributions are being recalculated correctly after an email is re-added and verified?

If a contribution-data rebuild is needed, is there a supported way to request one through Community?

The affected repository is private. I can provide exact commit IDs and API evidence through an appropriate private support channel.

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

[kaluarachchiteshan]

Hi,

Your checks are thorough. Since the commits are attributed to you by the API and are ancestors of main, the remaining suspects are profile settings and cached contribution data.

1. Private contributions must be enabled

All 492 of your contributions are reported as restricted, and the affected repository is private. Private repository activity only appears on the calendar if this is on:

• Open your profile → Contribution settings (the dropdown above the graph) → enable Private contributions.

Without it, those days can show zero even though the commits are attributed correctly.

2. Check the contribution rules for commits

A commit counts only if all of these are true:

• the author email is verified on your account (you did this)
• it was made in a standalone repository, not a fork, and on the default branch or gh-pages (you did this)
• you have access to the repository as owner, collaborator, or organization member, at the time GitHub processes it

If the repository belongs to an organization and your membership or access changed since the commits were made, the contributions may not be credited to you.

3. Timing of the backfill

When you add an email, GitHub backfills older commits asynchronously, and for large histories it can take longer than a day. Dates earlier than the email's verification can also behave differently from new commits. Note too that the calendar uses the commit's author timestamp and your profile time zone, so a commit near midnight can land on an adjacent day.

4. Things you can check or trigger yourself

• Remove and re-add the email only if you have already waited several days. Doing it repeatedly can restart the process.
• Make sure the email is not set as private in a way that stops matching: Settings → Emails, and check that "Keep my email addresses private" doesn't affect your older commits (it only affects new commits, but check the address list is correct).
• Compare the calendar on your profile signed out and signed in. Private contributions are shown only to you, and only with the setting above.

5. Escalation

Community members can't rebuild contribution data. If the setting above is enabled and several more days pass, contact GitHub Support (https://support.github.com/contact) and include:

• your username and the email, and the date you re-verified it
• the repository name and three example commit SHAs, shared only through the support form
• the API evidence: commits attributed to you, ancestors of main
• that the calendar shows 0 for September 2 and September 7, 2026
• a request for a contribution-data recalculation

Please don't post private repository names or commit SHAs in this public thread.