Introduce the GitHub Account Recovery Policy #758
Merged
Conversation
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.
Thank you for your interest in improving GitHub's site policies!
Context
This policy is being documented to codify and formalize existing practices regarding how GitHub handles account lockout recovery and to make clear that GitHub Support will not unlock accounts if the user has lost access to all approved means of account recovery. This policy makes clear GitHub's practices, established to protect users from social engineering and account theft.
This PR will remain open for feedback for a minimum of 24 hours as it does not introduce material changes to policy and simply codifies existing practice.