[Incident]: Profile rendering issues affecting GitHub profiles #203416
Replies: 78 comments 22 replies
|
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. |
|
Hi GitHub Community, I believe my issue may be related to this incident. My GitHub contribution graph is still showing contributions for commits that have already been removed from my repository history. The repository is I have verified that the remote repository is clean: git log origin/main --grep="test: activity"returns no results. git rev-list origin/main | wc -lreturns There are also no other remote branches containing those commits. However, the old contribution squares are still visible on my profile, even after more than 48 hours. When I click an affected day, it shows a contribution under So the contribution graph appears to be retaining stale contribution data for commits that are no longer present in the repository. I can provide screenshots of the affected contribution day and the unavailable commit if needed. Thanks! |
|
Hi GitHub team, I am experiencing the same profile achievement issue on @qingbo1011. "Show Achievements on my profile" is enabled and saved, but the Pull Shark achievement is still missing for both signed-in and public visitors. The following pull requests were authored by my account and merged by the upstream repository owner into the public repository default
The GitHub REST API reports both as merged, and GraphQL includes both pull requests in my contribution collection. More than 72 hours have passed since the second merge. However, my public profile still contains no native Achievements section or Pull Shark badge. Could you include this account in the profile achievement indexing investigation? Thank you. |
🆕 Community Manager Update: Monday August 17thHi everyone! Thank you for your patience and continuing to provide reports for this issue. The team is working on resolving this as soon as possible and I'll share more updates as they become available. |
|
Thank you for the update and for your continued work on this issue. The Achievements tab is now accessible on my profile, and I was also able to earn the Quickdraw achievement. However, the Pull Shark achievement is still not showing, despite my two pull requests having been successfully merged. It has now been six days since the qualifying pull requests were merged. Could you please confirm whether these pull requests meet the requirements for the Pull Shark achievement, or if there is any additional processing or delay that I should be aware of? Thank you again to the GitHub team for your time, support, and continued efforts to improve the platform. |
|
Hi GitHub team, I am experiencing the same profile achievement issue on @GuTS805. "Show Achievements on my profile" is enabled and saved, but the Pull Shark achievement is still missing for both signed-in and public visitors. The GitHub REST API reports both as merged, and GraphQL includes both pull requests in my contribution collection. More than 72 hours have passed since the second merge. However, my public profile still contains no native Achievements section or Pull Shark badge. Could you include this account in the profile achievement indexing investigation? Thank you. |
|
Hi GitHub team, I’m also experiencing this issue. I have 2 pull requests that were successfully merged into external repositories, but the Pull Shark achievement is still not appearing on my profile. My profile achievement settings are enabled. I’m sharing my case here as additional information for the investigation. Thank you for looking into this. |
|
Also affected: @YJ-928. Pull Shark not awarded after 2 merged PRs in a public repo |
|
Also affected: @basil-k-aji-dev. Pull Shark not awarded. Seven PRs I authored have been merged; six of them into the default branch of public repositories I do not own, across four separate days:
YOLO also not awarded: PRs #3–#7 in "Show Achievements on my profile" is enabled and Quickdraw renders correctly, so this is not a visibility-toggle problem. I have also tried hiding and unhiding a badge, which had no effect. One data point that may help narrow the trigger: Could my account be added to the achievement indexing investigation? |
|
my achievements is not coming and same with badges... please do resolve |
|
Hi GitHub team, Could you check whether my contribution-calendar discrepancy is related to this incident? Profile: https://github.com/realqadirx Repository: https://github.com/realqadirx/AURELIA-SkinCare-MakeUp-ProductStore After history rewriting, my profile displayed higher commit counts than the commits on origin/main, grouped by author date. During checks on September 16, 2026: Author date | Commits on origin/main | Profile displayed -- | -- | -- 2026-08-29 | 5 | 15 2026-08-31 | 4 | 20Local and remote main matched at the time. Support ticket #4762904 was closed with a referral to Community. The discrepancy remains unresolved. Could you help determine whether this is stale contribution data or expected counting behavior, and advise what additional evidence is needed? Thank you,
|
|
Adding another confirmed case that matches this incident, and specifically @SohailShabbir867's report above almost exactly. GitHub username: krenovv What happened:
What I've confirmed:
Affected repositories (all personal, not org-owned, no transfers involved):
Example commit I also opened a ticket through the Support form, but it was closed and pointed to these self-service resources (Community Discussions / Docs / Skills) instead — same outcome others in this thread have described. Happy to provide more commit SHAs or any other diagnostic info if it helps get this triaged. |
This appears to be more than a profile rendering issueThe reports in this discussion suggest that the problem may involve stale or inconsistent profile-derived data, rather than a purely client-side rendering problem. Several cases demonstrate that the underlying GitHub data is still correct while the profile presentation is not. For example:
That distinction is important because it suggests that the repository data itself is not necessarily the source of the problem. The affected information appears to be derived/indexed profile data that is consumed by the profile UI. For example, the report from Similarly, Note This makes me wonder whether the affected components share a common profile indexing/materialization pipeline rather than being independent UI bugs. If that is the case, repeatedly changing profile settings, recreating commits, or modifying repository history would not be expected to resolve the underlying problem. Those operations change the source data, while the affected profile representation may simply require a successful backend re-index/rebuild. It would therefore be useful if GitHub could clarify whether the investigation currently focuses on:
A useful diagnostic would also be to compare, for an affected account, the same activity across:
If those sources disagree, that would strongly indicate that the problem is occurring somewhere in the profile aggregation/indexing layer rather than in Git history itself. The fact that GitHub has acknowledged the issue and that the August 27 update says there is still no ETA makes the additional reports valuable, but it would be particularly helpful to know which subsystem is currently being investigated and whether a backend re-index is planned. Thanks to the GitHub team and everyone providing reproducible cases. The API-level observations and cross-checks are especially useful here because they help narrow the problem down considerably. |
|
Post-backfill data mismatch — @SiriLee (2026-09-18). Same pattern as @TPPPP72: Pull Shark was granted to my account today, but the recorded history doesn't match my actual activity.
REST verification: |
|
Hello GitHub team, I am also experiencing an issue on my profile were I have more than 30 merged coauthored requests but my Pair Extraordinaire badge was only updated to bronze not silver. Silver requires more than 24 merged coauthored requests and I have more than those. Your help would be very much appreciated, my username is @noel-mugisha. And also thank you for solving my pull shark achievement issue, it was well updated to silver |
|
Hi @ebndev , the newer reports in this thread seem to show that the issue may now involve more than profile rendering. Some users are reporting that achievements have started appearing again, but the achievement history/milestone associated with the badge can be incorrect. Others still have missing historical contributions even though the commits are correctly attributed and new contributions appear normally. That seems useful to distinguish between the profile UI and the underlying contribution/achievement processing. GitHub's documentation also notes that contribution graphs can require a rebuild, while Achievements are still a public-preview feature. It may be worth checking whether the affected accounts have inconsistent or stale profile-derived data rather than only a rendering/cache problem. If the team is already investigating the backend processing, comparing an affected account's repository/PR data with its profile contribution and achievement data could help identify where the mismatch occurs. Thanks for continuing to track this — the newer reports with exact timestamps and PR/commit references seem especially useful. |
|
ت |
|
My Pair Extraordinaire achievement hasn't rendered since the co-authored commit was merged on 2026-09-10. Evidence: Merged PR: TongyiDai/career-ops-zh#10 (base: main) Could this be a processing delay, or does the co-authored commit need to be the primary author to qualify? Please advise if anything is needed on my side. |
|
Follow-up on my report above (@basil-k-aji-dev, 17 Sep). The picture on my The failure window can be bracketed exactly on this account. Quickdraw unlocked at 2026-09-13 16:41:29 UTC — the timestamp is readable That gives a clean before/after pair on a single account, which is the
So on this account the counter appears never to have accumulated at all, rather Since then, 7 more PRs I authored have merged into public repositories I do not @SiriLee's report rules out one explanation, and it is worth saying so. Their granted trigger was SiriLee/dsh-rewind#25, labelled "2nd pull request The backfill has not reached this account. Several accounts report badges arriving on 2026-09-18, with the milestone Correction to my earlier comment. The first entry I listed, Also filed with Support. Happy to provide anything further from this account |
|
My Pair Extraordinaire achievement has not appeared despite meeting the requirements.
Could this account be included in the achievement reprocessing investigation? Looking forward to hearing from you. |
|
Update on my earlier reports (@basil-k-aji-dev). Pull Shark has now been granted — Still not granted on this account
Pair ExtraordinaireTwo merged commits on default branches carry a Both contain, verbatim: YOLOFive pull requests merged into the default branch of a public repository with zero reviews: Happy to provide anything else from this account that would help. @ebndev — noting this for a future update rather than asking for one: Pull Shark landed on this account on 2026-09-19, 46 days after the tier-1 threshold was met, while Pair Extraordinaire and YOLO have not. If badges are arriving unevenly rather than all at once, that may be useful signal for the team, and both outstanding cases above are checkable from the commit SHAs. |
|

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Community Manager Update: August 27, 2026
Hi again everyone!
We apologize for the delay. Due to other priorities and issues the team is working on, we don't currently have a timeline to share on when this will be fixed.
I will continue to follow up with the team and share additional details as I receive them.
Community Manager Update: Monday August 17th
Hi everyone! Thank you for your patience and continuing to provide reports for this issue.
The team is working on resolving this as soon as possible and I'll share more updates as they become available.
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