Contribution graph not updating after re-adding verified email

[0xMoni]

🏷️ Discussion Type

Question

Body

Hi github community,
I recently removed an email address (monikumari04428@gmail.com) from my GitHub account, then re-added and verified it. However, my contribution graph has not been restored to its previous state.

Before removing the email, I had approximately 114 contributions shown on my profile. After re-adding and verifying the email, only 14 contributions are showing. It has been several hours since re-verification.

Details:

• GitHub username: 0xMoni
• Email re-added and verified: monikumari04428@gmail.com
• Previous contribution count: ~114
• Current contribution count: 14
• Both emails on my account are verified

Could you please re-index or re-link my commits to restore my contribution graph? The commits still exist in my repositories; they're just not being counted on my profile.

Thank you for your help.

Best regards,
Moni Kumari

[Gana-Y]

Hey Moni,
This is a known issue with GitHub's contribution graph — removing and re-adding an email doesn't always trigger a full re-index of past commits.
A few things worth checking:
Make sure the email on your commits matches exactly what's verified on your account (you can check with git log --format="%ae" in your repos)
The graph can sometimes take up to 24 hours to update after re-verification, so give it a bit more time if you haven't already
That said, if it's still not showing after a day, the community here won't be able to fix it — you'll need to raise a ticket directly with GitHub Support at support.github.com. Just mention that you removed and re-added the email and ask them to re-index your contributions. They can actually trigger it on their end.
Your commits aren't lost, so don't worry — it's just a linking issue that support can sort out pretty quickly once you reach them.
Hope it gets resolved soon.

[Kavya20060702]

Step 1: Verify your local Git config
Make sure your future commits don't hit the same snag. Check that your local email matches your verified GitHub email exactly. Open your terminal and run:

Bash
git config --global user.email
If it doesn't match monikumari04428@gmail.com (or your other verified email), fix it by running:

Bash
git config --global user.email "monikumari04428@gmail.com"
Step 2: Trigger a manual rebuild of your graph
You can often force GitHub's cache to update without waiting. Try making a small change (like adding a space to a README file) directly on GitHub.com in one of your repositories and committing it. This sometimes forces the system to re-index your entire commit history for that email.

Step 3: Contact GitHub Support
If the graph doesn't update after a day, you will need to open a ticket directly with GitHub Support.

When opening the ticket, state:

"I temporarily removed and re-added my verified email (monikumari04428@gmail.com), which caused my contribution count to drop from 114 to 14. Can you please manually trigger a re-index of my contributions for my username 0xMoni?"

The support staff has a backend script that can rebuild your contribution cache in a few seconds!

[Vishayadav]

Hi Moni,

Contribution graphs are not usually restored instantly after an email is removed and then re-added. GitHub may take some time to reprocess and associate commits with the verified email address.

A few things to check:

• Ensure the commits were originally authored using the exact email address monikumari04428@gmail.com.
• Verify that the email is currently listed and verified in your GitHub account settings.
• Confirm that the repositories containing those commits are not private (unless private contribution display is enabled).
• Allow additional time for GitHub's systems to re-index contribution data.

Since the commits still exist and were previously counted, this may simply be a synchronization or re-indexing delay. If the contribution graph does not update after 24–48 hours, consider contacting GitHub Support directly.

I hope the issue resolves soon.

If this answer helps, please consider marking it as the accepted answer so that other users experiencing a similar problem can find it more easily.