Fix remaining references to moved Starlark configuration docs.
PiperOrigin-RevId: 452383140
Change-Id: I6e8fe59591da82e959cacfa34343e8cac8797546
diff --git a/site/en/docs/configurable-attributes.md b/site/en/docs/configurable-attributes.md
index 3b636c5..f2a20b9 100644
--- a/site/en/docs/configurable-attributes.md
+++ b/site/en/docs/configurable-attributes.md
@@ -207,7 +207,7 @@
)
```
-Behavior is the same as for [built-in flags](#built-in-flags). See [here](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/select_on_build_setting){: .external}
+Behavior is the same as for [built-in flags](#built-in-flags). See [here](https://github.com/bazelbuild/examples/tree/HEAD/configurations/select_on_build_setting){: .external}
for a working example.
[`--define`](/reference/command-line-reference#flag--define)
diff --git a/site/en/rules/config.md b/site/en/rules/config.md
index 336ec69..8c6f807 100644
--- a/site/en/rules/config.md
+++ b/site/en/rules/config.md
@@ -20,7 +20,7 @@
and more, all completely from .bzl files (no Bazel release required). See the
`bazelbuild/examples` repo for
-[examples](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations){: .external}.
+[examples](https://github.com/bazelbuild/examples/tree/HEAD/configurations){: .external}.
## User-defined build settings {:#user-defined-build-settings}
@@ -42,7 +42,7 @@
### Defining build settings {:#defining-build-settings}
-[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/basic_build_setting){: .external}
+[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/configurations/basic_build_setting){: .external}
#### The `build_setting` `rule()` parameter {:#rule-parameter}
@@ -172,7 +172,7 @@
### Predefined settings {:#predefined-settings}
-[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/use_skylib_build_setting){: .external}
+[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/configurations/use_skylib_build_setting){: .external}
The
[Skylib](https://github.com/bazelbuild/bazel-skylib){: .external}
@@ -313,7 +313,7 @@
### Label-typed build settings {:#label-typed-build-settings}
-[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/label_typed_build_setting){: .external}
+[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/configurations/label_typed_build_setting){: .external}
Unlike other build settings, label-typed settings cannot be defined using the
`build_setting` rule parameter. Instead, bazel has two built-in rules:
@@ -367,7 +367,7 @@
### Build settings and select() {:#build-settings-and-select}
-[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/select_on_build_setting){: .external}
+[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/configurations/select_on_build_setting){: .external}
Users can configure attributes on build settings by using
[`select()`](/reference/be/functions#select). Build setting targets can be passed to the `flag_values` attribute of
@@ -469,7 +469,7 @@
### Defining 1:2+ transitions {:#defining-1-2-transitions}
-[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/multi_arch_binary){: .external}
+[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/configurations/multi_arch_binary){: .external}
[Outgoing edge transition](#outgoing-edge-transitions) can map a single input
configuration to two or more output configurations. This is useful for defining
@@ -517,7 +517,7 @@
### Attaching transitions {:#attaching-transitions}
-[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/attaching_transitions_to_rules){: .external}
+[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/configurations/attaching_transitions_to_rules){: .external}
Transitions can be attached in two places: incoming edges and outgoing edges.
Effectively this means rules can transition their own configuration (incoming
@@ -562,7 +562,7 @@
### Transitions on native options {:#transitions-native-options}
-[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/transition_on_native_flag){: .external}
+[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/configurations/transition_on_native_flag){: .external}
Warning: Long term, the plan is to reimplement all native options as build
settings. When that happens, this syntax will be deprecated. Currently other
@@ -668,7 +668,7 @@
### Accessing attributes with transitions {:#accessing-attributes-with-transitions}
-[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations/read_attr_in_transition){: .external}
+[End to end example](https://github.com/bazelbuild/examples/tree/HEAD/configurations/read_attr_in_transition){: .external}
When [attaching a transition to an outgoing edge](#outgoing-edge-transitions)
(regardless of whether the transition is a 1:1 or 1:2+ transition), `ctx.attr` is forced to be a list
@@ -734,7 +734,7 @@
})
```
-See [complete example](https://github.com/bazelbuild/examples/tree/main/rules/starlark_configurations/multi_arch_binary)
+See [complete example](https://github.com/bazelbuild/examples/tree/main/configurations/multi_arch_binary)
here.
## Integration with platforms and toolchains {:#integration-platforms-toolchains}
@@ -809,4 +809,4 @@
* [Starlark Build Configuration](https://docs.google.com/document/d/1vc8v-kXjvgZOdQdnxPTaV0rrLxtP2XwnD2tAZlYJOqw/edit?usp=sharing){: .external}
* [Bazel Configurability Roadmap](https://bazel.build/roadmaps/configuration.html){: .external}
- * Full [set](https://github.com/bazelbuild/examples/tree/HEAD/rules/starlark_configurations){: .external} of end to end examples
+ * Full [set](https://github.com/bazelbuild/examples/tree/HEAD/configurations){: .external} of end to end examples
