Change URLs to bazelbuild

--
MOS_MIGRATED_REVID=102022958

10 files changed, 27 insertions, 27 deletions

diff --git a/site/blog/_posts/2015-04-06-Simplified-Workspace-Creation.md b/site/blog/_posts/2015-04-06-Simplified-Workspace-Creation.md
index e75ae06010..ea5a67b560 100644
--- a/site/blog/_posts/2015-04-06-Simplified-Workspace-Creation.md
+++ b/site/blog/_posts/2015-04-06-Simplified-Workspace-Creation.md
@@ -34,4 +34,4 @@ setting up your workspace.
 
 Let us know if you have any questions or issues on the
 [mailing list](https://groups.google.com/forum/#!forum/bazel-discuss) or
-[GitHub](https://github.com/google/bazel).
+[GitHub](https://github.com/bazelbuild/bazel).
diff --git a/site/blog/_posts/2015-04-10-bash-completion.md b/site/blog/_posts/2015-04-10-bash-completion.md
index 5ee45d0c6e..0a5d842fd7 100644
--- a/site/blog/_posts/2015-04-10-bash-completion.md
+++ b/site/blog/_posts/2015-04-10-bash-completion.md
@@ -28,7 +28,7 @@ command in your shell and see the list of possible completions.
 If you are interested in supporting other shells, the script is made up
 of two parts:
 
-1. [`scripts/bazel-complete-header.bash`](https://github.com/google/bazel/blob/master/scripts/bazel-complete-template.bash)
+1. [`scripts/bazel-complete-header.bash`](https://github.com/bazelbuild/bazel/blob/master/scripts/bazel-complete-template.bash)
   is the completion logic.
 2. `bazel info completion` dumps the list of commands of Bazel, their options
   and for commands and options that expect a value, a description of what is
@@ -48,4 +48,4 @@ of two parts:
 
 Let us know if you have any questions or issues on the
 [mailing list](https://groups.google.com/forum/#!forum/bazel-discuss) or
-[GitHub](https://github.com/google/bazel).
+[GitHub](https://github.com/bazelbuild/bazel).
diff --git a/site/blog/_posts/2015-07-08-Java-Configuration.md b/site/blog/_posts/2015-07-08-Java-Configuration.md
index 858ca0c6fa..f9beef32e7 100644
--- a/site/blog/_posts/2015-07-08-Java-Configuration.md
+++ b/site/blog/_posts/2015-07-08-Java-Configuration.md
@@ -15,7 +15,7 @@ build --javacopt="-target 8"
 
 However, the file would becomes quickly overloaded, especially if you take
 all languages and options into account. Instead, you can tweak the
-[java_toolchain](https://github.com/google/bazel/tree/0e1680e58f01f3d443f7e68865b5a56b76c9dadf/tools/jdk/BUILD#L73)
+[java_toolchain](https://github.com/bazelbuild/bazel/tree/0e1680e58f01f3d443f7e68865b5a56b76c9dadf/tools/jdk/BUILD#L73)
 rule that specifies the various options for the java compiler. So in a
 BUILD file:
 
diff --git a/site/blog/_posts/2015-07-28-docker_build.md b/site/blog/_posts/2015-07-28-docker_build.md
index a1fd26ca5a..055c9cd32e 100644
--- a/site/blog/_posts/2015-07-28-docker_build.md
+++ b/site/blog/_posts/2015-07-28-docker_build.md
@@ -16,7 +16,7 @@ image. However, V1 Docker build suffers several issues:
 
 Googlers working on [Google Container Registry](https://gcr.io) developed a support
 for building reproducible Docker images using Skylark / Bazel that address these
-problems. We recently [shipped](https://github.com/google/bazel/commit/5f25891bb17d19cb1208ddad1e88cc4bb4a56782)
+problems. We recently [shipped](https://github.com/bazelbuild/bazel/commit/5f25891bb17d19cb1208ddad1e88cc4bb4a56782)
 it.
 
 Of course, it does not support `RUN` command, but the rule also strips
@@ -63,4 +63,4 @@ to fetch the various base image for the web and we are working on providing a
 `docker_pull` rule to interact more fluently with existing images.
 
 You can learn more about this docker support
-[here](https://github.com/google/bazel/blob/master/tools/build_defs/docker/README.md).
+[here](https://github.com/bazelbuild/bazel/blob/master/tools/build_defs/docker/README.md).
diff --git a/site/blog/_posts/2015-07-29-dashboard-dogfood.md b/site/blog/_posts/2015-07-29-dashboard-dogfood.md
index 9fdcbdb706..b9d8901d9d 100644
--- a/site/blog/_posts/2015-07-29-dashboard-dogfood.md
+++ b/site/blog/_posts/2015-07-29-dashboard-dogfood.md
@@ -28,7 +28,7 @@ http://localhost:8080/ (each build will print a unique URL to visit).
 
 <img src="/assets/dash-shell.png"/>
 
-See [the README](https://github.com/google/bazel/blob/master/src/tools/dash/README.md)
+See [the README](https://github.com/bazelbuild/bazel/blob/master/src/tools/dash/README.md)
 for documentation.
 
 This is very much a work in progress. Please let us know if you have any
diff --git a/site/docs/install.md b/site/docs/install.md
index 4d4a174e64..277be17d61 100644
--- a/site/docs/install.md
+++ b/site/docs/install.md
@@ -58,7 +58,7 @@ $ sudo gcc --version
 
 ## Download Bazel
 
-Download the [Bazel installer](https://github.com/google/bazel/releases) for
+Download the [Bazel installer](https://github.com/bazelbuild/bazel/releases) for
 your operating system.
 
 ## Run the installer
diff --git a/site/docs/supported-rules.md b/site/docs/supported-rules.md
index 6523bede9b..71d76320fb 100644
--- a/site/docs/supported-rules.md
+++ b/site/docs/supported-rules.md
@@ -8,14 +8,14 @@ The Bazel team provides a set of supported build rules written using the
 [Skylark](/docs/skylark/index.html) rules framework. These rules allow you
 to build the following:
 
-*   [Closure libraries](https://github.com/google/bazel/tree/master/tools/build_rules/closure)
-*   [Docker images](https://github.com/google/bazel/tree/master/tools/build_defs/docker)
-*   [Groovy projects](https://github.com/google/bazel/tree/master/tools/build_defs/groovy)
-*   [Java App Engine applications](https://github.com/google/bazel/tree/master/tools/build_rules/appengine)
-*   [Rust projects](https://github.com/google/bazel/tree/master/tools/build_rules/rust)
+*   [Closure libraries](https://github.com/bazelbuild/bazel/tree/master/tools/build_rules/closure)
+*   [Docker images](https://github.com/bazelbuild/bazel/tree/master/tools/build_defs/docker)
+*   [Groovy projects](https://github.com/bazelbuild/bazel/tree/master/tools/build_defs/groovy)
+*   [Java App Engine applications](https://github.com/bazelbuild/bazel/tree/master/tools/build_rules/appengine)
+*   [Rust projects](https://github.com/bazelbuild/bazel/tree/master/tools/build_rules/rust)
 
 The source for these rules are located in the
-[tools/build_rules](https://github.com/google/bazel/tree/master/tools/build_rules)
+[tools/build_rules](https://github.com/bazelbuild/bazel/tree/master/tools/build_rules)
 and
-[tools/build_defs](https://github.com/google/bazel/tree/master/tools/build_defs)
+[tools/build_defs](https://github.com/bazelbuild/bazel/tree/master/tools/build_defs)
 directories in the Bazel GitHub repo.
diff --git a/site/faq.md b/site/faq.md
index 59dd0c5e23..12def68fa6 100644
--- a/site/faq.md
+++ b/site/faq.md
@@ -157,12 +157,12 @@ Can I see examples?
 
 Yes. For a simple example, see:
 
-  <https://github.com/google/bazel/blob/master/examples/cpp/BUILD>
+  <https://github.com/bazelbuild/bazel/blob/master/examples/cpp/BUILD>
 
 The Bazel source code itself provides more complex examples:
 
-  <https://github.com/google/bazel/blob/master/src/main/java/BUILD>\\
-  <https://github.com/google/bazel/blob/master/src/test/java/BUILD>
+  <https://github.com/bazelbuild/bazel/blob/master/src/main/java/BUILD>\\
+  <https://github.com/bazelbuild/bazel/blob/master/src/test/java/BUILD>
 
 What is Bazel best at?
 ----------------------
@@ -286,7 +286,7 @@ Can I build Docker images with Bazel?
 -------------------------------------
 
 Yes, you can use our
-[Docker rules](https://github.com/google/bazel/blob/master/tools/build_defs/docker/README.md)
+[Docker rules](https://github.com/bazelbuild/bazel/blob/master/tools/build_defs/docker/README.md)
 to build reproducible Docker images.
 
 Will Bazel make my builds reproducible automatically?
@@ -357,14 +357,14 @@ It is possible to write Python rules as extensions (see below). See
 the following files for an example of generating self-contained zip
 files for python:
 
-  <https://github.com/google/bazel/blob/master/tools/build_rules/py_rules.bzl>\\
-  <https://github.com/google/bazel/tree/master/examples/py>
+  <https://github.com/bazelbuild/bazel/blob/master/tools/build_rules/py_rules.bzl>\\
+  <https://github.com/bazelbuild/bazel/tree/master/examples/py>
 
 We are working on opening up a subset of our internal Python rules, so
 they can be used as helper scripts as part of a build.
 
 Simplistic support for PEX-style binaries is at
-[here](https://github.com/google/bazel/blob/master/tools/build_rules/py_rules.bzl).
+[here](https://github.com/bazelbuild/bazel/blob/master/tools/build_rules/py_rules.bzl).
 
 
 What about Go?
@@ -390,8 +390,8 @@ At present, however, the extension mechanism is experimental.
 
 For the following languages, we have experimental rules:
 
-   * [Rust](https://github.com/google/bazel/blob/master/tools/build_rules/rust/README.md)
-   * [Closure](https://github.com/google/bazel/blob/master/tools/build_rules/closure/README.md)
+   * [Rust](https://github.com/bazelbuild/bazel/blob/master/tools/build_rules/rust/README.md)
+   * [Closure](https://github.com/bazelbuild/bazel/blob/master/tools/build_rules/closure/README.md)
 
 I need more functionality. Can I add rules that are compiled into Bazel?
 ------------------------------------------------------------------------
@@ -421,7 +421,7 @@ Where do I report bugs?
 -----------------------
 
 Send an e-mail to <bazel-discuss@googlegroups.com> or file a bug
-[on GitHub](https://github.com/google/bazel/issues).
+[on GitHub](https://github.com/bazelbuild/bazel/issues).
 
 
 
diff --git a/site/roadmap.md b/site/roadmap.md
index cb851e82be..090bc7df30 100644
--- a/site/roadmap.md
+++ b/site/roadmap.md
@@ -14,7 +14,7 @@ repositories:
 
 *   A Google-internal repository, containing both Bazel code and
     Google-specific extensions and features
-*   An external [GitHub repository](https://github.com/google/bazel),
+*   An external [GitHub repository](https://github.com/bazelbuild/bazel),
     containing only the Bazel code.
 
 We anticipate making the external repository *primary* in the future, that is,
diff --git a/site/support.md b/site/support.md
index 04e0fafe7b..85f5dc7004 100644
--- a/site/support.md
+++ b/site/support.md
@@ -16,7 +16,7 @@ subject to change at any time without prior notice. The Skylark macro and rules
 you write in a `.bzl` file) is still subject to change.
 
 Bugs can be reported in the
-[GitHub bugtracker](https://github.com/google/bazel/issues). We will make an effort to triage all
+[GitHub bugtracker](https://github.com/bazelbuild/bazel/issues). We will make an effort to triage all
 reported issues within 2 business days.
 
 ## Releases