summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPetros Amiridis <petros@amiridis.net>2011-06-10 09:59:31 +0300
committerPetros Amiridis <petros@amiridis.net>2011-06-10 10:35:07 +0300
commitd2ad14b6954055a466ea4fb20a44e49e331dab3a (patch)
treec350201c2ffe10853d2aae6657384c07c889b03c
parenta7639fe62f04f7879aa3da1774684c4113aac10e (diff)
added caveats sections to transfering a repository
-rw-r--r--_posts/2008-01-06-move-a-repo.markdown10
1 files changed, 10 insertions, 0 deletions
diff --git a/_posts/2008-01-06-move-a-repo.markdown b/_posts/2008-01-06-move-a-repo.markdown
index a757587..99ef964 100644
--- a/_posts/2008-01-06-move-a-repo.markdown
+++ b/_posts/2008-01-06-move-a-repo.markdown
@@ -14,6 +14,16 @@ You can transfer ownership of a repository you own in the Admin page of your rep
![Type in the new owner and click the "Tranfer" button.](/images/danger_zone_transfer.jpg)
+There are a few caveats, especially with regards to private repos:
+
+* The target user must not have a repository with the same name, or a fork in the same network.
+* If the repository is private the target user must have a paid account with at least one unused private repository available.
+* Private forks cannot be transferred, only root private repos.
+
+We cannot set up redirects with git, so every clone of the repository will need to have its remote updated. All you need to run to update your local repository is
+
+ git remote set-url remote_name new_url
+
Existing forks
--------------