Historical contribution graph missing after moving verified commit email between GitHub accounts

[Misba-404]

Account: Misba-404

Historical commit:
Misba-404/JavaScript
c48ae965df5a86bf3508ddc063d78558cacef20b

Author email in .patch:
misbah.in05@gmail.com

The email was previously associated with another GitHub account.
I removed it from that account and added/verified it on Misba-404.

The commit page now correctly shows:
Misba-404 committed

The commit is on the repository's default branch:
main

More than 28 hours have passed.

New commits using the same email are appearing on my contribution graph,
but historical contributions made before the email was moved remain missing.

GitHub Support ticket: 4773317
Support closed the ticket and directed me to Community Discussions/Docs.

Is there a way to trigger/rebuild the historical contribution graph?

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.

[sajusman]

Also facing similar issue

[ioannisman]

Exactly the same problem here.
My ticket (4785108) was automatically closed and I was directed here.

[TeWei02]

The contribution graph is keyed off the commit's author email, and GitHub stores an attribution for each commit the first time it processes it. Moving the address from the old account to yours does not retroactively rewrite those older records, so new commits land on Misba-404 while the historical ones stay credited to whichever account owned the email at the time. They are not gone, just attached elsewhere.

Four conditions have to hold, and any one of them blocks attribution permanently:

• the email is verified on the account
• the commit sits on the default branch or gh-pages (yours is on main, so that part is fine)
• the repository is standalone, not a fork
• you own or collaborate on it, or you forked / opened an issue or PR / starred it

You satisfy all four, which is exactly why commits made after the move do show up. But the automatic recalc window is roughly 24 hours, and by the time the address landed on your account that window had already closed for the older pushes; it does not get queued again on its own. Support closing the ticket is normal too, they do not edit contribution data by hand.

What actually forces a re-evaluation is changing the commit SHAs. GitHub already holds an attribution record for the existing commit objects, so simply re-pushing them does nothing. With git filter-repo:

pip install git-filter-repo
git clone https://github.com/Misba-404/JavaScript.git
cd JavaScript
git filter-repo --name-callback 'return b"Misba-404"' --email-callback 'return b"misbah.in05@gmail.com"'
git push --force --all
git push --force --tags

Two things worth knowing before you run that:

• every SHA changes, so anyone who already cloned the repo has to re-clone. On a personal repo that is usually a non-issue.
• if the address is still verified on the other account, remove it there first. When one address belongs to two accounts the attribution is ambiguous, and it tends to keep resolving to the older owner.

Once the rewritten push lands the historical commits should populate within a day. If they still do not, the duplicate verification on the other account is almost always the reason.

[sajusman]

I had done everything correctly. The issue was on GitHub’s side the cache hadn’t refreshed. The AI let me through to a human, and they fixed it.