bazel-contrib · promptless · Oct 19, 2025 · Oct 19, 2025 · Oct 19, 2025 · Oct 22, 2025
diff --git a/6.5.0/community/roadmaps-build-api.mdx b/6.5.0/community/roadmaps-build-api.mdx
@@ -1,4 +1,4 @@
-<style>
+{/* <style>
   .padbottom { padding-bottom: 10px; }
   .etabox {
     background: #EFEFEF;
@@ -24,7 +24,7 @@
     font-weight: bold;
     padding-left: 10px;
   }
-</style>
+</style> */}
 ---
 title: 'Bazel Build API 2021 Roadmap'
 ---
@@ -53,14 +53,14 @@ the particular language. Remove language specific logic from Bazel’s core.
 The Java rules will first be rewritten to Starlark and tested internally on a
 large code-base. After that they will be released to Bazel.
 
-<div class="padbottom"></div>
-<span class="etabox">Q1 2021</span>
+&nbsp;
+**Q1 2021**
 
 *   Improve the **Java sandwich**, making it possible to rewrite existing Java
     rules. <span class="donestatus">DONE</span>
 
-<div class="padbottom"></div>
-<span class="etabox">Q2 2021</span>
+&nbsp;
+**Q2 2021**
 
 *   Improve Starlark support for **native libraries** in Java.
     <span class="inprogressstatus">IN PROGRESS</span>
@@ -70,21 +70,21 @@ large code-base. After that they will be released to Bazel.
 *   **java_library** rule is Starlarkified. <span class="inprogressstatus">IN
     PROGRESS</span>
 
-<div class="padbottom"></div>
-<span class="etabox">Mid 2021</span>
+&nbsp;
+**Mid 2021**
 
 *   **java_binary and java_test** rules are Starlarkified.
 *   **java_import and java_plugin** rules are Starlarkified.
 
-<div class="padbottom"></div>
-<span class="etabox">Fall 2021</span>
+&nbsp;
+**Fall 2021**
 
 *   Starlarkification of **java_\*_proto_library**
 *   Remaining java rules are Starlarkified: **java_package_configuration,
     java_runtime, java_toolchain**.
 
-<div class="padbottom"></div>
-<span class="etabox">2022</span>
+&nbsp;
+**2022**
 
 *   Starlarkification of **java_common module**.
 
@@ -95,30 +95,30 @@ After that the C++ rules will be rewritten to Starlark piece by piece using
 builtins functionality. The API for C++ rules will not be made accessible from
 .bzl files until cc_module is rewritten in Starlark as well.
 
-<div class="padbottom"></div>
-<span class="etabox">Q1 2021</span>
+&nbsp;
+**Q1 2021**
 
-*   **Clang modules** support, <span class="droppedstatus">DROPPED*</span>
+*   **Clang modules** support, <span class="droppedstatus">DROPPED</span>
 *   and **Include scanning** support, expected performance improvements from
-    both <span class="droppedstatus">DROPPED*</span>
+    both <span class="droppedstatus">DROPPED</span>
 *   *We need more data to evaluate whether modules are really what is needed to
     improve performance.
 
-<div class="padbottom"></div>
-<span class="etabox">Q2 2021</span>
+&nbsp;
+**Q2 2021**
 
 *   Internal **Go rules** are Starlarkified <span class="inprogressstatus">IN
     PROGRESS</span>
 *   Objective-C rules **objc_library and objc_import** and native code related
     to them are Starlarkified <span class="inprogressstatus">IN PROGRESS</span>
 
-<div class="padbottom"></div>
-<span class="etabox">Fall 2021 and beginning 2022</span>
+&nbsp;
+**Fall 2021 and beginning 2022**
 
 *   **cc_binary, cc_test and cc_library** are Starlarkified
 
-<div class="padbottom"></div>
-<span class="etabox">2022</span>
+&nbsp;
+**2022**
 
 *   Starlarkification of other C++ rules (**fdo_profile, cc_import,
     cc_toolchain, cc_toolchain_suite, fdo_prefetch_hints, cc_toolchain_alias,
@@ -127,8 +127,8 @@ builtins functionality. The API for C++ rules will not be made accessible from
 
 ## Misc
 
-<div class="padbottom"></div>
-<span class="etabox">Mid 2021</span>
+&nbsp;
+**Mid 2021**
 
 *   Aspect can propagate other aspects - proposal
     [Aspects Propagating Other Aspects](https://docs.google.com/document/d/1fVNyskIgMoiNeOOGt57LdDmEkAShkYUKYQTkf5yD1fA/edit).

diff --git a/6.5.0/external/advanced.mdx b/6.5.0/external/advanced.mdx
@@ -43,7 +43,7 @@ http_archive(
 )
 ```
 
-B/WORKSPACE {# This is not a buganizer link okay?? #}
+B/WORKSPACE {/* This is not a buganizer link okay?? */}
 
 ```python
 workspace(name = "B")

diff --git a/6.5.0/query/cquery.mdx b/6.5.0/query/cquery.mdx
@@ -533,7 +533,7 @@ different niches. Consider the following to decide which is right for you:
     that `query` avoids. For example,
     if `"//foo"` exists in two configurations, which one
     should `cquery "deps(//foo)"` use?
-    The `[config](#config)`</code> function can help with this.
+    The `[config](#config)` function can help with this.
 *   As a newer tool, `cquery` lacks support for certain use
     cases. See [Known issues](#known-issues) for details.
 

diff --git a/7.6.1/external/advanced.mdx b/7.6.1/external/advanced.mdx
@@ -43,7 +43,7 @@ http_archive(
 )
 ```
 
-B/WORKSPACE {# This is not a buganizer link okay?? #}
+B/WORKSPACE {/* This is not a buganizer link okay?? */}
 
 ```python
 workspace(name = "B")

diff --git a/8.0.1/external/advanced.mdx b/8.0.1/external/advanced.mdx
@@ -43,7 +43,7 @@ http_archive(
 )
 ```
 
-B/WORKSPACE {# This is not a buganizer link okay?? #}
+B/WORKSPACE {/* This is not a buganizer link okay?? */}
 
 ```python
 workspace(name = "B")

diff --git a/8.1.1/external/advanced.mdx b/8.1.1/external/advanced.mdx
@@ -43,7 +43,7 @@ http_archive(
 )
 ```
 
-B/WORKSPACE {# This is not a buganizer link okay?? #}
+B/WORKSPACE {/* This is not a buganizer link okay?? */}
 
 ```python
 workspace(name = "B")

diff --git a/8.2.1/external/advanced.mdx b/8.2.1/external/advanced.mdx
@@ -43,7 +43,7 @@ http_archive(
 )
 ```
 
-B/WORKSPACE {# This is not a buganizer link okay?? #}
+B/WORKSPACE {/* This is not a buganizer link okay?? */}
 
 ```python
 workspace(name = "B")

diff --git a/8.3.1/external/advanced.mdx b/8.3.1/external/advanced.mdx
@@ -43,7 +43,7 @@ http_archive(
 )
 ```
 
-B/WORKSPACE {# This is not a buganizer link okay?? #}
+B/WORKSPACE {/* This is not a buganizer link okay?? */}
 
 ```python
 workspace(name = "B")

diff --git a/8.4.2/external/advanced.mdx b/8.4.2/external/advanced.mdx
@@ -43,7 +43,7 @@ http_archive(
 )
 ```
 
-B/WORKSPACE {# This is not a buganizer link okay?? #}
+B/WORKSPACE {/* This is not a buganizer link okay?? */}
 
 ```python
 workspace(name = "B")

diff --git a/reference/be/functions.mdx b/reference/be/functions.mdx
@@ -533,7 +533,7 @@ that counts the number of lines in the file.
     name = "count_lines_" + f[:-3],  # strip ".cc"
     srcs = [f],
     outs = ["%s-linecount.txt" % f[:-3]],
-    cmd = "wc -l $< >$@",
+    cmd = "wc -l $&lt; &gt;$@",
  ) for f in glob(["*_test.cc"])]
 
 ```
@@ -614,10 +614,7 @@ Notes:
    is left out, some other rule must match to avoid an error.
 
 - `select` can be embedded _inside_ a larger
-   attribute assignment. So `srcs = ["common.sh"]
-      + select({ ":conditionA": ["myrule_a.sh"], ...})` and `
-      srcs = select({ ":conditionA": ["a.sh"]}) + select({ ":conditionB":
-      ["b.sh"]})` are valid expressions.
+   attribute assignment. So `srcs = ["common.sh"] + select({":conditionA": ["myrule_a.sh"], ...})` and `srcs = select({":conditionA": ["a.sh"]}) + select({":conditionB": ["b.sh"]})` are valid expressions.
 
 - `select` works with most, but not all, attributes. Incompatible
    attributes are marked `nonconfigurable` in their documentation.

diff --git a/reference/be/platforms-and-toolchains.mdx b/reference/be/platforms-and-toolchains.mdx
@@ -229,7 +229,7 @@ is a parent platform:
     `remote_execution_properties` will be used.
 
 2. If `remote_execution_property` is set on the child platform, and contains the
-    literal string {PARENT\_REMOTE\_EXECUTION\_PROPERTIES}, that macro will be
+    literal string `{PARENT\_REMOTE\_EXECUTION\_PROPERTIES}`, that macro will be
     replaced with the contents of the parent's `remote_execution_property` attribute.
 
 3. If `remote_execution_property` is set on the child platform, and does not contain
@@ -360,7 +360,7 @@ cpu architecture to be both `@platforms//cpu:x86_64` and
 
 `exec_properties`
 
-Dictionary: String -> String; [nonconfigurable](common-definitions.html#configurable-attributes); default is `{}`
+Dictionary: `String -> String`; [nonconfigurable](common-definitions.html#configurable-attributes); default is `{}`
 
  A map of strings that affect the way actions are executed remotely. Bazel makes no attempt
  to interpret this, it is treated as opaque data that's forwarded via the Platform field of
@@ -407,7 +407,7 @@ String; [nonconfigurable](common-definitions.html#configurable-attributes); defa
  A string used to configure a remote execution platform. Actual builds make no attempt to
  interpret this, it is treated as opaque data that can be used by a specific SpawnRunner.
  This can include data from the parent platform's "remote\_execution\_properties" attribute,
- by using the macro "{PARENT\_REMOTE\_EXECUTION\_PROPERTIES}". See the section on
+ by using the macro `"{PARENT\_REMOTE\_EXECUTION\_PROPERTIES}"`. See the section on
  [Platform Inheritance](#platform_inheritance) for details.
 
  `required_settings`