The great Skylark -> Starlark class migration:
Replace all known remaining references*
*Except java_rules_skylark.bzl. This is depended on in third_party/jformatstring (https://github.com/bazelbuild/bazel/blob/a8353612b4791531ae4e2ed463cf0e5d8a4009e8/third_party/jformatstring/BUILD#L17), so breaking the dependency is a bit more complex.
I'm excluding as part of this migration project:
- "skylark" in URLs. We can't just break URLs. And our docs generation pipeline may bake in assumptions. This would have to be its own docs effort.
- "skylark-lang", etc. build targets that alandonovan@ is migrating to java.net.starlark.
- --skylark_* builds flags. Changing these without warning is higher risk since we don't know who uses these flags for what. These should go through their own dedicated migration processes.
PiperOrigin-RevId: 326283275
diff --git a/src/test/shell/integration/modify_execution_info_test.sh b/src/test/shell/integration/modify_execution_info_test.sh
index 61b0ab5..0a061d3 100755
--- a/src/test/shell/integration/modify_execution_info_test.sh
+++ b/src/test/shell/integration/modify_execution_info_test.sh
@@ -187,9 +187,9 @@
fi
local pkg="${FUNCNAME[0]}"
mkdir -p "$pkg" || fail "mkdir -p $pkg"
- echo "load('//$pkg:shell.bzl', 'skylark_shell')" > "$pkg/BUILD"
+ echo "load('//$pkg:shell.bzl', 'starlark_shell')" > "$pkg/BUILD"
cat >> "$pkg/BUILD" <<'EOF'
-skylark_shell(
+starlark_shell(
name = "shelly",
output = "ok.txt",
)
@@ -220,7 +220,7 @@
command = "touch %s" % ctx.outputs.output.path,
)
-skylark_shell = rule(
+starlark_shell = rule(
_impl,
attrs = {
"output": attr.output(mandatory=True),
