Docs should mention the new no-remote-cache-upload tag (bazelbuild#15965)

sgowroji · Googler · web-flow · commit e4ee34416ef1 · 2022-07-25T10:44:18.000+05:30
Fixes : bazelbuild#14518 PiperOrigin-RevId: 462641379 Change-Id: I152bb90be4951e2a68973967f0370aaed059dd7b Co-authored-by: Googler <noreply@google.com>
diff --git a/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html b/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html
@@ -42,10 +42,13 @@
     executed remotely (but it may be cached remotely).
   </li>
 
-  <li><code>no-remote</code> keyword prevents the action or test from being executed remotely
-    or cached remotely. This is equivalent to using both no-remote-cache and no-remote-exec.
+  <li><code>no-remote</code> keyword prevents the action or test from being executed remotely or
+    cached remotely. This is equivalent to using both
+    <code>no-remote-cache</code> and <code>no-remote-exec</code>.
+      </li>
+   <li><code>no-remote-cache-upload</code> keyword disables upload part of remote caching of a spawn.
+     it does not disable remote execution.
   </li>
-
     <li><code>local</code> keyword precludes the action or test from being remotely cached,
     remotely executed, or run inside the sandbox.
     For genrules and tests, marking the rule with the <code>local = True</code>
