Add org policy to prevent accidental repo transfer#1069
Open
aduh95 wants to merge 3 commits into
Open
Conversation
GitHub has a feature to limit repository transfers which we could take advantage of
targos
approved these changes
Jun 9, 2026
marco-ippolito
approved these changes
Jun 9, 2026
aduh95
commented
Jun 9, 2026
aduh95
commented
Jun 9, 2026
richardlau
approved these changes
Jun 9, 2026
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
4 participants
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.
GitHub has a feature to limit repository transfers which we could take advantage of. Accidental transfers (or at least transfers that did not follow the process) is certainly something that has happened, and while they are generally not a big deal, it's probably better to raise the bar to make malicious account takeover less appealing.
I've just tried it, here's what it looks like when trying to make a repository change:
Looks like we need to define who the approvers, TSC would be the logical group.
Refs: https://docs.github.com/en/enterprise-cloud@latest/enterprise-onboarding/govern-people-and-repositories/create-repository-policies