The evidence you listed covers the visible prerequisites: a public repository, a co-authored commit, a valid trailer, and the commit merged into the default branch. There is no user-facing reindex or “grant achievement” action to run after that.

Before escalating, check the exact raw commit message on GitHub, not only the local message. The trailer must be a separate footer line in this form:

Co-authored-by: Name <[email protected]>

and the co-author email must be verified on the co-author account. Since GitHub already renders both accounts as authors, that part is likely fine.

If the profile badge still has not appeared after a reasonable processing delay, open GitHub Support with the repository URL, PR, full commit SHA, default-branch name, and a link to the raw commit message. Achievements are processed by GitHub; a community member cannot backfill one. I would not create artificial extra co-authored commits just to force the badge, because that makes the actual eligibility case harder to inspect.

Hello @Behruz-A,

Since GitHub recognizes both accounts on commit 2ae614a and the Co-Authored-By trailer is correctly formatted, the technical setup of your commit is correct.

Here are the most likely reasons the Pair Extraordinaire achievement has not appeared yet:

1. Processing Delays

GitHub's achievement engine runs in background batches and does not update instantaneously. It frequently takes 24 to 48 hours for the Pair Extraordinaire badge to be awarded after a qualifying pull request is merged. If you just merged PR #1 recently, waiting is the most likely solution.

2. The Squash Merge Caveat

GitHub only awards the badge based on the final commit that lands in the default branch. If you used the "Squash and merge" option to close the pull request, GitHub bundles the PR into a brand-new commit. If the Co-Authored-By trailer was accidentally deleted from the commit message box during the squash process, the final merge will not trigger the badge.

• To verify this, navigate directly to the master branch in Behruz-A/practice, open the commit history, and check the commit message for the final merge to ensure the trailer is still visible.

3. The Repository is a Fork

Achievements like Pair Extraordinaire and Pull Shark are only awarded for pull requests merged into a root (standalone) repository.

• To verify this is not the issue, look at the top-left corner of the Behruz-A/practice repository page. If it says "forked from [another-repo]", this merge will not count toward the achievement.

4. Profile UI Caching

If 48 hours have passed and the final commit on master definitely contains the trailer, your GitHub profile might be serving a cached state. You can force the UI to refresh.

1. Open Profile Settings: Navigation.
   Navigate to your GitHub account settings and select Public profile. You will know you are in the right place if you see your profile picture and bio options.

2. Toggle Achievements Off:
   Scroll down to the Achievements section, uncheck "Show Achievements on my profile", and click Save. You can verify this worked by viewing your public profile; the badges section will be completely hidden.

3. Toggle Achievements On:
   Re-check the box and click Save again to trigger the backend to rebuild your profile cache. You can verify this by checking your profile to see if the badge has now appeared.

To help me narrow this down if the badge still does not appear, how long ago was PR #1 merged, and did you use a standard merge or a squash merge?