From 3b577f0655cb4f281b4ae0a3b46f8352daa111ef Mon Sep 17 00:00:00 2001 From: lesleyanneb <31181282+lesleyanneb@users.noreply.github.com> Date: Tue, 10 Aug 2021 21:17:12 +1000 Subject: [PATCH] Update transferring-a-repository.md (#20723) * Update transferring-a-repository.md * Update content/github/administering-a-repository/managing-repository-settings/transferring-a-repository.md Co-authored-by: hubwriter --- .../managing-repository-settings/transferring-a-repository.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/github/administering-a-repository/managing-repository-settings/transferring-a-repository.md b/content/github/administering-a-repository/managing-repository-settings/transferring-a-repository.md index c9efc59a12..7b6dc7ff31 100644 --- a/content/github/administering-a-repository/managing-repository-settings/transferring-a-repository.md +++ b/content/github/administering-a-repository/managing-repository-settings/transferring-a-repository.md @@ -48,6 +48,8 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc $ git remote set-url origin new_url ``` +- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." + For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." ### Repository transfers and organizations