From c31e7b40841da14639095dc981f28eeee65294cc Mon Sep 17 00:00:00 2001 From: Armando Montanez Date: Wed, 12 Aug 2026 14:18:28 -0700 Subject: [PATCH] docs: Fix unclosed code block in repository options RELNOTES: None --- .../devtools/build/lib/bazel/repository/RepositoryOptions.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryOptions.java b/src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryOptions.java index 46df9b7ea57747..6c5d93a1dad83a 100644 --- a/src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryOptions.java +++ b/src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryOptions.java @@ -292,7 +292,7 @@ verified by hashes stored in the registry (and thus pinned by the lockfile). This file consists of directives, one per line, that adjust how the Bazel downloader acts. The directives are: `allow`, `block`, `rewrite`, and `all_blocked_message`. The directives are applied in the order - `rewrite, allow, block'. + `rewrite, allow, block`. Comments are allowed and must be on their own line (no trailing comments) and preceded by a `#`. Example: `# evil.com is known to host malicious code`