Clarify asynchronous batch latency for newly unlocked profile achievements - #46118
Closed
UmeshCode1 wants to merge 1 commit into
Closed
UmeshCode1 wants to merge 1 commit into
UmeshCode1 wants to merge 1 commit into
Conversation
1 task
Contributor
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
Contributor
|
Closing per #46115 (comment) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why:
Closes: #46115
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. Adding this clarification sets expectations and deflects repetitive inquiry threads across GitHub Community and Support.
What's being changed:
Adds a bullet point to the
[!NOTE]incontent/account-and-profile/reference/profile-reference.mdclarifying that achievements are evaluated and awarded by an asynchronous background process and typically take 24 to 48 hours to reflect on a user profile.Check off the following: