chore: replace bazelbuild with bazel-contrib

This was done using `grep | xargs sed`.

Author: rickeylev

BZLMOD_SUPPORT.md

@@ -11,7 +11,7 @@ In general `bzlmod` has more features than `WORKSPACE` and users are encouraged
 
 ## Configuration
 
-The releases page will give you the latest version number, and a basic example.  The release page is located [here](/bazelbuild/rules_python/releases).
+The releases page will give you the latest version number, and a basic example.  The release page is located [here](/bazel-contrib/rules_python/releases).
 
 ## What is bzlmod?
 
@@ -53,7 +53,7 @@ better supported.
 the toolchains rules_python registers**.
 
 NOTE: Regardless of your toolchain, due to
-[#691](https://github.com/bazelbuild/rules_python/issues/691), `rules_python`
+[#691](https://github.com/bazel-contrib/rules_python/issues/691), `rules_python`
 still relies on a local Python being available to bootstrap the program before
 handing over execution to the toolchain Python.
 

CHANGELOG.md

@@ -30,7 +30,7 @@ the [GitHub `gh` tool](https://github.com/cli/cli)
 (More advanced users may prefer the GitHub UI and raw `git` commands).
 
 ```shell
-gh repo fork bazelbuild/rules_python --clone --remote
+gh repo fork bazel-contrib/rules_python --clone --remote
 ```
 
 Next, make sure you have a new enough version of Python installed that supports the

CONTRIBUTING.md

@@ -32,7 +32,7 @@ other minor changes bump the patch digit.
 To find if there were any features added or incompatible changes made, review
 [CHANGELOG.md](CHANGELOG.md) and the commit history. This can be done using
 github by going to the url:
-`https://github.com/bazelbuild/rules_python/compare/<VERSION>...main`.
+`https://github.com/bazel-contrib/rules_python/compare/<VERSION>...main`.
 
 ## Patch release with cherry picks
 

RELEASING.md

@@ -107,7 +107,7 @@ local_repository(
 # which we need to fetch in order to compile it.
 load("@rules_python_gazelle_plugin//:deps.bzl", _py_gazelle_deps = "gazelle_deps")
 
-# See: https://github.com/bazelbuild/rules_python/blob/main/gazelle/README.md
+# See: https://github.com/bazel-contrib/rules_python/blob/main/gazelle/README.md
 # This rule loads and compiles various go dependencies that running gazelle
 # for python requirements.
 _py_gazelle_deps()
@@ -118,7 +118,7 @@ interpreter = "@python_3_11_9_host//:python"
 #####################
 # Install twine for our own runfiles wheel publishing.
 # Eventually we might want to install twine automatically for users too, see:
-# https://github.com/bazelbuild/rules_python/issues/1016.
+# https://github.com/bazel-contrib/rules_python/issues/1016.
 load("@rules_python//python:pip.bzl", "pip_parse")
 
 pip_parse(

WORKSPACE

@@ -266,7 +266,7 @@ Determines if relative symlinks are created using `declare_symlink()` at build
 time.
 
 This is only intended to work around
-[#2489](https://github.com/bazelbuild/rules_python/issues/2489), where some
+[#2489](https://github.com/bazel-contrib/rules_python/issues/2489), where some
 packaging rules don't support `declare_symlink()` artifacts.
 
 Values:

docs/api/rules_python/python/config_settings/index.md

@@ -104,7 +104,7 @@
         # Insert after the main extension
         extensions.insert(1, "readthedocs_ext.external_version_warning")
         readthedocs_vcs_url = (
-            "http://github.com/bazelbuild/rules_python/pull/{}".format(
+            "http://github.com/bazel-contrib/rules_python/pull/{}".format(
                 os.environ.get("READTHEDOCS_VERSION", "")
             )
         )
@@ -133,7 +133,7 @@
 
 # --- Extlinks configuration
 extlinks = {
-    "gh-path": (f"https://github.com/bazelbuild/rules_python/tree/main/%s", "%s"),
+    "gh-path": (f"https://github.com/bazel-contrib/rules_python/tree/main/%s", "%s"),
 }
 
 # --- MyST configuration

docs/conf.py

@@ -23,7 +23,7 @@ Extending the core rules is most useful when you want all or most of the
 behavior of a core rule.
 :::
 
-Follow or comment on https://github.com/bazelbuild/rules_python/issues/1647
+Follow or comment on https://github.com/bazel-contrib/rules_python/issues/1647
 for the development of APIs to support custom derived rules.
 
 ## Creating custom rules

docs/extending.md

@@ -18,7 +18,7 @@ your MODULE.bazel file:
 
 ```starlark
 # Update the version "0.0.0" to the release found here:
-# https://github.com/bazelbuild/rules_python/releases.
+# https://github.com/bazel-contrib/rules_python/releases.
 bazel_dep(name = "rules_python", version = "0.0.0")
 
 pip = use_extension("@rules_python//python/extensions:pip.bzl", "pip")
@@ -39,13 +39,13 @@ using Bzlmod. Here is a simplified setup to download the prebuilt runtimes.
 load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
 
 # Update the snippet based on the latest release below
-# https://github.com/bazelbuild/rules_python/releases
+# https://github.com/bazel-contrib/rules_python/releases
 
 http_archive(
     name = "rules_python",
     sha256 = "ca77768989a7f311186a29747e3e95c936a41dffac779aff6b443db22290d913",
     strip_prefix = "rules_python-0.36.0",
-    url = "https://github.com/bazelbuild/rules_python/releases/download/0.36.0/rules_python-0.36.0.tar.gz",
+    url = "https://github.com/bazel-contrib/rules_python/releases/download/0.36.0/rules_python-0.36.0.tar.gz",
 )
 
 load("@rules_python//python:repositories.bzl", "py_repositories")

docs/getting-started.md

@@ -71,7 +71,7 @@ In some cases you may not want to generate the requirements.bzl file as a reposi
 while Bazel is fetching dependencies. For example, if you produce a reusable Bazel module
 such as a ruleset, you may want to include the requirements.bzl file rather than make your users
 install the WORKSPACE setup to generate it.
-See https://github.com/bazelbuild/rules_python/issues/608
+See https://github.com/bazel-contrib/rules_python/issues/608
 
 This is the same workflow as Gazelle, which creates `go_repository` rules with
 [`update-repos`](https://github.com/bazelbuild/bazel-gazelle#update-repos)
@@ -180,7 +180,7 @@ buildozer command:
 buildozer 'substitute deps @old//([^/]+) @new//${1}' //...:*
 ```
 
-[requirements-drawbacks]: https://github.com/bazelbuild/rules_python/issues/414
+[requirements-drawbacks]: https://github.com/bazel-contrib/rules_python/issues/414
 
 ### Entry points