Fixes Contribtuors PR doc

1 files changed, 1 insertions, 88 deletions

diff --git a/contributors/guide/github-workflow.md b/contributors/guide/github-workflow.md
index 60bde11f..01ae6e80 100644
--- a/contributors/guide/github-workflow.md
+++ b/contributors/guide/github-workflow.md
@@ -74,95 +74,8 @@ git checkout -b myfeature
 Then edit code on the `myfeature` branch.
 
 #### Build
-The following section is a quick start on how to build Kubernetes locally, for more detailed information you can see [kubernetes/build](https://git.k8s.io/kubernetes/build/README.md).
-The best way to validate your current setup is to build a small part of Kubernetes. This way you can address issues without waiting for the full build to complete. To build a specific part of Kubernetes use the `WHAT` environment variable to let the build scripts know you want to build only a certain package/executable.
 
-```sh
-make WHAT=cmd/{$package_you_want}
-```
-
-*Note:* This applies to all top level folders under kubernetes/cmd.
-
-So for the cli, you can run:
-
-```sh
-make WHAT=cmd/kubectl
-```
-
-If everything checks out you will have an executable in the `_output/bin` directory to play around with.
-
-*Note:* If you are using `CDPATH`, you must either start it with a leading colon, or unset the variable. The make rules and scripts to build require the current directory to come first on the CD search path in order to properly navigate between directories.
-
-```sh
-cd $working_dir/kubernetes
-make
-```
-
-To remove the limit on the number of errors the Go compiler reports (default
-limit is 10 errors):
-```sh
-make GOGCFLAGS="-e"
-```
-
-To build with optimizations disabled (enables use of source debug tools):
-
-```sh
-make GOGCFLAGS="-N -l"
-```
-
-To build binaries for all platforms:
-
-```sh
-make cross
-```
-
-#### Install etcd
-
-```sh
-cd $working_dir/kubernetes
-
-# Installs in ./third_party/etcd
-hack/install-etcd.sh
-
-# Add to PATH
-echo export PATH="\$PATH:$working_dir/kubernetes/third_party/etcd" >> ~/.profile
-```
-
-#### Test
-
-```sh
-cd $working_dir/kubernetes
-
-# Run all the presubmission verification. Then, run a specific update script (hack/update-*.sh)
-# for each failed verification. For example:
-#   hack/update-gofmt.sh (to make sure all files are correctly formatted, usually needed when you add new files)
-#   hack/update-bazel.sh (to update bazel build related files, usually needed when you add or remove imports)
-make verify
-
-# Alternatively, run all update scripts to avoid fixing verification failures one by one.
-make update
-
-# Run every unit test
-make test
-
-# Run package tests verbosely
-make test WHAT=./pkg/api/helper GOFLAGS=-v
-
-# Run integration tests, requires etcd
-# For more info, visit https://git.k8s.io/community/contributors/devel/sig-testing/testing.md#integration-tests
-make test-integration
-
-# Run e2e tests by building test binaries, turn up a test cluster, run all tests, and tear the cluster down
-# Equivalent to: go run hack/e2e.go -- -v --build --up --test --down
-# Note: running all e2e tests takes a LONG time! To run specific e2e tests, visit:
-# https://git.k8s.io/community/contributors/devel/sig-testing/e2e-tests.md#building-kubernetes-and-running-the-tests
-make test-e2e
-```
-
-See the [testing guide](/contributors/devel/sig-testing/testing.md) and [end-to-end tests](/contributors/devel/sig-testing/e2e-tests.md)
-for additional information and scenarios.
-
-Run `make help` for additional information on these make targets.
+This workflow is process-specific; for quick start build instructions for [kubernetes/kubernetes](https://git.k8s.io/kubernetes) please [see here](/contributors/devel/development.md#building-kubernetes-on-a-local-osshell-environment).
 
 ### 4 Keep your branch in sync