Clarify 24–48 hour asynchronous batch latency for newly unlocked profile achievements

[UmeshCode1]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-achievements-on-your-profile

What part(s) of the article would you like to see updated?

Add a [!NOTE] callout regarding the asynchronous reconciliation latency (24–48 hours) for newly qualified achievements:

[!NOTE]
Achievements are evaluated and awarded by an asynchronous background process. After qualifying criteria are met (such as a merged pull request or an accepted discussion answer in a public repository), it typically takes 24 to 48 hours for new badges and tier updates to reflect on your profile.

Why should the docs be changed?

In community/community, one of the most frequent support questions from new open-source contributors is "Why hasn't my Pull Shark / Pair Extraordinaire badge appeared after my PR was merged?" (e.g. discussions #209029, #208902).

Currently, the article outlines how achievements work and which activities qualify, but does not state that badge minting is asynchronous rather than instantaneous upon merge. This leads contributors to assume the badge system is broken or that their PR did not register.

Additional information

Adding this single note directly sets expectations for new developers and deflects repetitive inquiry threads across GitHub Community and Support.

[UmeshCode1]

Submitted pull request #46118 with this clarification added directly under the Earning Achievements section of content/account-and-profile/reference/profile-reference.md.

[subatoi]

I will raise this with the appropriate team internally to see if it's something they'd like to add to the public-facing content, but since the two community discussions highlighted here are 1 and 2 days old respectively, it's not something we're going to action at this time and I'm going to close this and the associated PR out.