Thanks Hopefully as soon as possible

Joined

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 HelloWorld. I accidentally pushed a series of generated commits and later reset main to my last legitimate commit and force-pushed the corrected history.

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 -l

returns 2.

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 HelloWorld, but clicking the commit leads to a page with no commit history because the commit has already been removed.

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 main branch:

1. feat: 按会话控制发送后的已读上报并完善新版兼容 starccy/feishu-unreadme#9 — merged at 2026-08-12 04:04 UTC
2. fix: 适配飞书 7.73.9 的已读上报入口 starccy/feishu-unreadme#10 — merged at 2026-08-13 02:49 UTC

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

Subject: Pair Extraordinaire achievement not upgrading despite multiple co-authored merged PRs

Hello GitHub Team,

My GitHub username is @ManoharPaturi.

My Pair Extraordinaire achievement was unlocked on October 12, 2026, but it is still displaying the basic level and shows "Coauthored with an unknown user."

I have multiple co-authored commits associated with merged pull requests across major public repositories.

I independently identified at least 27 distinct commits involving other human co-authors across several upstream projects.

Examples:

Microsoft PyRIT

• FIX: refetch server default labels when the runtime generation changes microsoft/PyRIT#2874
• FIX: clamp TemplateSegmentConverter split count for short prompts microsoft/PyRIT#2840
• FIX: krippendorff_alpha NaN for unpairable identical ratings microsoft/PyRIT#2844

NVIDIA NeMo Run

• fix(cli): only treat delimited run/executor/plugins prefixes as overwrites NVIDIA-NeMo/Run#605
• fix(cli): forward entrypoint skip_confirmation to the generated command NVIDIA-NeMo/Run#609
• fix(cli): remove stray "Configuring global options" debug print NVIDIA-NeMo/Run#611

NVIDIA NeMo Curator

• fix(modules): treat DocumentSplitter separator as a literal string NVIDIA-NeMo/Curator#2376
• fix(utils): split_large_files RecursionError on single row larger than target size NVIDIA-NeMo/Curator#2377

My GitHub profile:
https://github.com/ManoharPaturi

Could you please:

1. Verify which co-authored merged pull requests qualify for Pair Extraordinaire?
2. Confirm why the badge is still showing the basic level?
3. Check whether my account is affected by the acknowledged achievement-processing incident ([Incident]: Profile rendering issues affecting GitHub profiles #203416)?
4. Reprocess or correct my achievement record if appropriate?

I can provide additional commit SHAs and screenshots if required.

Thank you for your help.

Hi GitHub team, I am experiencing the missing Pull Shark achievement issue on @jianrec.

I authored these two pull requests in DefuzeX-AI/AgentBehaviorBench, and both were merged by @YiWang24 into main:

The GitHub GraphQL API confirms state: MERGED, merged: true, and author jianrec for both PRs. The repository is currently public, is not a fork, and its default branch is main.

As of October 14, about six days after the merges, my public achievements page shows YOLO but still does not show Pull Shark:
https://github.com/jianrec?tab=achievements

I submitted GitHub Support ticket #4856160 today with these details. It was closed because my account's available support options are self-service resources, including Community Discussions; I did not receive a determination about whether these PRs were counted.

Could the team include my account in this investigation, verify whether these PRs qualify and were processed correctly, and correct or reindex the achievement record if needed?

Thank you.

Hi GitHub team,

I'm having an issue with achievements on my account, @zhechen-cs. My profile currently shows only Pull Shark, but I have several contributions that seem to qualify for other achievements.

Quickdraw: I created and merged [PR #1](zhechen-cs/great-tree-meadow#1) on October 4, 2026, within 4 minutes and 25 seconds.

YOLO: Both [PR #1](zhechen-cs/great-tree-meadow#1) and [PR #2](zhechen-cs/great-tree-meadow#2) were merged by my own account without any submitted reviews.

Pair Extraordinaire: This [merged PR](TheDoctorZoose/CITS3403-Agile-Project#44) from May 2025 contains a [co-authored commit](TheDoctorZoose/CITS3403-Agile-Project@9f279ed) linked to my GitHub user ID (112833940). My username was previously ChenZhez.

I also now have 17 merged PRs, all in public repositories and merged into their default branches. I understand the Pull Shark Bronze tier may still be processing, since my latest merges were on October 14.

Could someone check whether these contributions qualify and whether my account is affected by the ongoing achievement processing issue? I'd appreciate it if any missing achievements could be reprocessed.

Thanks!

Hello GitHub Support,

I would like to request a manual review and unlock of my Pair Extraordinaire achievement.

I have a merged pull request containing commits with a valid Co-authored-by attribution. I believe this pull request meets the requirements for the Pair Extraordinaire achievement, but the achievement has not yet been awarded to my GitHub profile.

The Pull request was merged into the repository's dev branch about one week ago. Despite the merge and the co-author attribution being present in the commit history, I have not received the achievement.

Here is the relevant commits. The complete commit record, including the Co-authored-by information, can be viewed directly from the URL.

Could you please manually review the relevant commits and, if they meet the requirements for the Pair Extraordinaire achievement, unlock the achievement for my account?

Thank you for your help.

Hello team,

I'm experiencing the same issue with the Pull Shark achievement on my Github profile, despite having merged four pull requests into public repositories, the achievement is not showing.

Here the links:
Card-Forge/forge#11178
jupnp/jupnp#367
Card-Forge/forge#11317
Card-Forge/forge#11459

Could you please check if my account is eligible for the achievement or if I'm missing something?

Best,
Giovanni

Same issue here on @HSM-03.

• Pull Shark: 3 PRs merged into main of a public repo on 2026-10-11
  (Add Korean text to README HSM-03/Pull_Shark#1, Feature Request: Select a column when adding an issue to a project #2, Feature request: support jumping to lines in files #5)
• Pair Extraordinaire: co-authored commit in merged PR Feature request: support jumping to lines in files #5, co-author
  correctly linked to @chiikawaaii
  (HSM-03/Pull_Shark@8289bf9)
  It is missing on both my profile and @chiikawaaii's.

YOLO and Quickdraw were awarded normally, but these two never appeared.
My Support ticket (#4867501) was also closed with self-service resources.

https://github.com/orgs/community/discussions/210474

Pull Shark x3 — Incorrect 128th Merged PR Attribution (Verified API Evidence)

Hello GitHub Team,

I am reporting a potential milestone attribution issue with my Pull Shark x3 (Silver) achievement.

My GitHub username is @ozankenangungor.

My Pull Shark x3 achievement has now been awarded successfully. However, the achievement history associates the 128th merged pull request milestone with a PR that does not match the chronological merge order recorded by GitHub's own APIs.

Currently displayed milestone:

ozankenangungor/release-engineer#24 — 128th pull request merged

ozankenangungor/release-engineer#24

Expected milestone based on chronological merge order:

rust-lang/rust#162432 — 128th pull request merged

rust-lang/rust#162432

1. Verified API Evidence

On October 15, 2026, I collected evidence using the authenticated GitHub CLI.

Both GitHub REST and GraphQL APIs independently confirmed 128 merged pull requests authored by my account.

Actual terminal results:

Captured UTC: 2026-10-15T20:44:04Z
GitHub user: ozankenangungor

Authenticated GitHub Search API total_count: 128
Unique merged PRs in two API pages: 128

GitHub Search API public count: 54
GitHub Search API private count: 74

GitHub user GraphQL merged PR totalCount: 128

These results were generated directly from GitHub's APIs, not estimated from profile activity.

2. Chronological Merge Order Discrepancy

I retrieved all 128 merged PR records and sorted them by their merged_at timestamps.

Currently attributed PR — Release Engineer #24:

Repository: ozankenangungor/release-engineer
PR number: 24
Author: ozankenangungor
Merged: true
Merged at: 2026-10-09T02:52:30Z
Chronological merge position: 120 / 128

Expected PR — Rust #162432:

Repository: rust-lang/rust
PR number: 162432
Author: ozankenangungor
Merged: true
Merged at: 2026-10-15T15:27:22Z
Chronological merge position: 128 / 128
Target branch: main
Repository visibility: Public

The Rust PR was accepted and merged into the official Rust programming language repository.

It is the 128th merged PR when all 128 recorded merges are ordered chronologically.

3. Requested Correction

I understand that GitHub's achievement system may use internal eligibility rules or processing order that differ from raw chronological merge order.

Nevertheless, the milestone currently displayed on my profile does not match the chronological sequence recorded by GitHub's APIs.

I am requesting that the GitHub Achievements engineering team:

1. Review the milestone attribution associated with my Pull Shark x3 achievement.
2. Investigate why release-engineer#24, the 120th PR by merge timestamp, is displayed as the 128th merged PR.
3. Reconcile the achievement's milestone history with the qualifying PR records.
4. If the milestone is intended to reflect chronological merge order and the Rust contribution qualifies, update the displayed milestone link to rust-lang/rust#162432.

This is not a request for another achievement or a higher tier. My Pull Shark x3 achievement has already been awarded.

I am specifically requesting a correction to the pull request associated with the existing Silver achievement.

The Rust contribution is especially meaningful to me because it was accepted into the official Rust programming language repository, and I would like my achievement history to accurately reflect the milestone.

4. Supporting Evidence

I have prepared the following evidence:

• Authenticated GitHub REST API results
• Independent GitHub GraphQL results
• A chronological comparison
  of the two PRs
• Public PR links and merge timestamps
• A screenshot showing the current incorrect milestone attribution

The relevant evidence is attached.

Please review this attribution discrepancy and forward it to the team responsible for GitHub Achievements if appropriate.

Thank you for your time and assistance.
summary_SHAREABLE.txt
milestone_comparison_SHAREABLE.txt

Hi GitHub team,

My account is @andremellotech. Quickdraw appeared successfully,
but Pull Shark is still missing.

I authored these two PRs, both merged on October 16, 2026:
andremellotech/mello-charts-desktop#1
andremellotech/mello-charts-desktop#2

Both are in my own public repository. Could you confirm whether
they qualify and whether my account is affected by the achievement
processing issue?

Thank you.

Hi GitHub team,

Could you check achievement eligibility and processing for
my account, @andremellotech?

Quickdraw is visible, but Pull Shark and YOLO are missing.

These PRs were authored and merged by me on October 16, 2026,
in my own public repository, with no code reviews recorded:

andremellotech/mello-charts-desktop#1
andremellotech/mello-charts-desktop#2
andremellotech/mello-charts-desktop#5

Could you confirm whether these events qualify and whether
my account is affected by this incident? If they qualify,
please investigate the missing achievements.

Thank you.

Possible achievement earning/display delay for khalil-official

Profile: https://github.com/khalil-official
Checked publicly on October 19, 2026 at 06:04:06 UTC (achievements tab:
Quickdraw only; unchanged from earlier checks on the same day).

I am reporting this for comparison with the September 23 update about
delays both earning achievements and displaying them. I cannot establish
whether this account is affected by that incident or whether additional
achievements qualify.

The account has authored thirteen merged public pull requests (full
inventory with mergedAt/mergedBy/review states saved locally from the
GraphQL API on October 19, 2026). These are all in repositories owned by
the same account; I am not claiming that this establishes eligibility for
Pull Shark. Community discussions such as #18294, #18476 and #179161
indicate own-repository merges count toward Pull Shark, but that is
community observation, not an official rule, and I understand merge counts
alone do not establish GitHub's internal eligibility decision. Examples
with independently visible merge records:

• Fix DMD eigenvalue reconstruction and rank-deficient input failures khalil-official/modal-current#2 — merged October 18, 2026, 01:20:57 UTC; a tested DMD reconstruction/rank validation fix.
• Deliver conditioned exchanger profiles with verified animated results khalil-official/thermal-streams#1 — merged October 18, 2026, 00:53:35 UTC.
• Publish verified pipe-flow diagnostics with actual bisection animation khalil-official/pipeflow-bench#1 — merged October 18, 2026, 01:00:42 UTC.
• Deliver verified channel-flow studies and readable computed animation khalil-official/channel-lattice#1 — merged October 18, 2026, 17:39:50 UTC.
• Deliver reproducible hard and soft IC droplet PINN comparisons khalil-official/droplet-pinn-studio#1 — merged October 18, 2026, 17:39:54 UTC.

These PRs have Copilot COMMENTED reviews, so I am not reporting them as
unreviewed merges. No claim is being made about YOLO or other achievements.
I have not yet confirmed whether any additional earned badge is
individually hidden in the signed-in profile.

For context, October reports in the incident thread and in discussion
#208079 describe Pull Shark missing months after qualifying merges and
tiers stuck below observed merge counts, so a delay or counting anomaly
rather than ineligibility seems plausible for this account too — but that
remains unconfirmed.

Could the responsible team check whether any achievement events for
khalil-official are pending or affected by the incident, or clarify
whether there is simply no additional qualifying award yet?

Update on my registration (kittimzhe — registered Oct 3): still zero movement on my side, but the picture is sharper now — this looks like selective non-recovery rather than queue delay.

My pending triggers, all verified in place:

• YOLO: PR Welcome to GitHub product feedback #1 merged Sep 18 09:02 UTC (0 reviews) and PR Feature Request: Select a column when adding an issue to a project #2 merged Sep 22 06:01 UTC (0 reviews), both in a public repo — still unissued
• Galaxy Brain: accepted-answer marks on Sep 24/25 (How to keep version numbers in sync across many files in a project? #208018, How do I give read-only access to some users in another department? #208139) and Oct 13 (Pull Shark achievement missing despite 17 merged public PRs #209607) — still unissued (2 qualifying answers since Sep 25)

Why this looks selective: registrants from both older cohorts (Sep 14/17 registrations whose badges are now live) and younger ones (a user whose qualifying merges happened Oct 11 has all five badges as of today) have visibly recovered — I checked current badge states today. Every one of my triggers predates several recovered cases, yet none of mine has issued.

In case the original events were dropped rather than delayed, I re-triggered YOLO today with a fresh 0-review merge (PR #3, merged Oct 20 09:11 UTC, public repo). If fresh triggers process while the old ones stay silent, that would confirm the lost-event failure mode for this account.

Title: Contribution Graph Has Not Updated Since October 13, 2026

Hello GitHub Support and Community,

My GitHub contribution graph has stopped updating since October 13, 2026.

I have made multiple commits after October 13, and all of them are visible in my repositories' commit history. However, these commits are not appearing as green contribution squares on my GitHub profile.

Everything was working normally before this issue started. I have not changed my Git configuration or workflow. The problem appeared suddenly, and even contributions older than 24 hours are still missing.

I have checked my repositories, and the commits are present. This makes me suspect that there may be an issue with GitHub's contribution processing or profile data updates.

Could you please investigate this issue and clarify whether it is a known problem affecting other users?

Issue details:

• Last date contributions appeared: October 13, 2026
• Issue noticed: October 20, 2026
• Commits are visible in repository history: Yes
• Contributions appear on my profile graph: No
• Recent Git configuration or workflow changes: None

Thank you for your time and assistance.

Hello GitHub team,

Could you check achievement eligibility and processing for my account, @shoaibulhaque?

As of October 21, 2026, my public profile displays Pull Shark and Quickdraw. Pair Extraordinaire and YOLO are not publicly visible. I understand there is an existing achievement-processing incident, and I would like to provide concrete examples for investigation.

Pair Extraordinaire

• PR: fix: align setup dependencies and model paths hariskhan-hk/Tumor_Classification#1
• Merged: October 16, 2026, at 08:36:26 UTC, into the default main branch.
• Repository: public, not a fork.
• Co-authored commit: hariskhan-hk/Tumor_Classification@9adda17
• GitHub's commit author information resolves both shoaibulhaque and hariskhan-hk.
• The commit contains the co-author trailer and is an ancestor of the current default branch. My author email is verified.

YOLO

• PR: docs: index every language and explain how to use the examples shoaibulhaque/CheatSheets#12
• Merged: October 16, 2026, at 07:50:00 UTC, into the default main branch.
• Repository: public, not a fork.
• PR author and merging account: shoaibulhaque.
• Submitted reviews: zero.

I can provide the corresponding REST and GraphQL results if useful.

Could you confirm whether these events qualify and whether they have been processed for my account? If the records are stuck, please investigate whether they can be reprocessed.

Thank you.