[Incident]: Profile rendering issues affecting GitHub profiles #203416
Replies: 9 comments
|
Hi! Accepting PR for this issue? |
|
Thanks Hopefully as soon as possible |
|
Thanks for the update, hopefully this gets fixed soon. |
|
Joined |
|
Hello GitHub Community, I’m experiencing an issue where all of my historical GitHub contributions associated with one of my verified email addresses disappeared from my contribution graph. My GitHub username: Affected email: Here is what happened: On August 6, 2026, at approximately 2:21 AM, I accidentally removed the email address: This email address had previously been used as the author email for many of my Git commits. Shortly afterward, I added the EXACT SAME email address back to my GitHub account and verified it successfully. However, after re-adding the email, all historical contributions associated with that email disappeared from my contribution graph. This is NOT limited to one repository. Contributions from approximately 15+ repositories that were previously attributed to this email are affected. What I have already done:
Example affected commit:
From: Sohail Shabbir unknownperson23414@gmail.com The important point is that the email is now verified and attached to my account, but the historical contributions that were previously associated with this email are still missing. New commits are appearing correctly, so my account and contribution graph are currently working. The problem appears to be specifically with historical commits created before I removed and re-added the email address. I have also checked my GitHub email settings and the exact email address is currently present and verified. Has anyone experienced the same issue after accidentally removing and then re-adding a commit email address? Is there anything else I can do to restore the historical contributions, or does this require GitHub Support to manually rebuild/re-index the contribution history? I would really appreciate any advice or confirmation from someone who has experienced this before. Thank you! |
|
Username: aniketshukla1 I have at least five public pull requests authored by this account and marked merged: floci-io/floci#2031 |
|
Adding my case here since it matches what I've seen others reporting. I have 5 merged PRs that meet Pull Shark's criteria (authored by me, merged into the default branch of repos I don't own):
Verified commit email, "Show Achievements" enabled, no badge ever appeared. With the "Show Achievements" setting disabled, my profile shows a banner saying "You unlocked new Achievements on GitHub! Show them off by updating your Profile settings" pointing at the general achievements toggle. When I toggled that setting on, the banner changed to a different message: "You unlocked new Achievements with private contributions! Show them off by including private contributions in your Profile settings", pointing at a completely different setting. I enabled that too. Still nothing renders. So the backend appears to know achievements have unlocked (it's actively telling me so, twice, with two different explanations), but nothing is displaying regardless of which settings are toggled on or off. |
|
Please fix it. Everyone in the world is using GitHub, but you can't fix a simple issue. For me too, both badges are not showing |
|
I’m experiencing this as well. My GitHub profile is not displaying achievements that I should have unlocked, despite the relevant PRs being merged and my settings being enabled. This appears to match the profile/achievement rendering issue described here. Happy to provide specific PRs or other details if useful. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
We've received multiple reports about profile pages rendering differently than expected, including:
We've escalated these reports to the appropriate team.
At this time, we don't have an estimated timeline for a fix or additional information to share. Please subscribe to this thread to receive updates as they become available.
If you're experiencing this issue and have additional information you'd like to share, leave a comment below.
Thank you for your patience while we investigate.
All reactions