summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Bailey <robertbailey@google.com>2015-08-12 13:12:32 -0700
committerRobert Bailey <robertbailey@google.com>2015-08-12 13:12:32 -0700
commit36a2019fe707de032c352ffe1375cf476564ef53 (patch)
tree946966d56fceeba3427e039cdebe2faa2c9a6d9b
parenta577fe59554100f7339e4784089095734875afd5 (diff)
Update repository links in development.md.
-rw-r--r--development.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/development.md b/development.md
index 294f825a..db74adaf 100644
--- a/development.md
+++ b/development.md
@@ -51,7 +51,7 @@ Below, we outline one of the more common git workflows that core developers use.
### Fork the main repository
-1. Go to https://github.com/GoogleCloudPlatform/kubernetes
+1. Go to https://github.com/kubernetes/kubernetes
2. Click the "Fork" button (at the top right)
### Clone your fork
@@ -64,7 +64,7 @@ cd $GOPATH/src/k8s.io
# Replace "$YOUR_GITHUB_USERNAME" below with your github username
git clone https://github.com/$YOUR_GITHUB_USERNAME/kubernetes.git
cd kubernetes
-git remote add upstream 'https://github.com/GoogleCloudPlatform/kubernetes.git'
+git remote add upstream 'https://github.com/kubernetes/kubernetes.git'
```
### Create a branch and make changes
@@ -81,7 +81,7 @@ git fetch upstream
git rebase upstream/master
```
-Note: If you have write access to the main repository at github.com/GoogleCloudPlatform/kubernetes, you should modify your git configuration so that you can't accidentally push to upstream:
+Note: If you have write access to the main repository at github.com/kubernetes/kubernetes, you should modify your git configuration so that you can't accidentally push to upstream:
```sh
git remote set-url --push upstream no_push
@@ -166,7 +166,7 @@ export GOPATH=$KPATH
3) Populate your new GOPATH.
```sh
-cd $KPATH/src/github.com/GoogleCloudPlatform/kubernetes
+cd $KPATH/src/github.com/kubernetes/kubernetes
godep restore
```