Suggest including a debugging=False parameter that controlled debug logging as an alternative to removing the debug logging.

--
MOS_MIGRATED_REVID=132570566

1 files changed, 6 insertions, 5 deletions

diff --git a/site/versions/master/docs/skylark/macros.md b/site/versions/master/docs/skylark/macros.md
index 6242af8d1a..467c818550 100644
--- a/site/versions/master/docs/skylark/macros.md
+++ b/site/versions/master/docs/skylark/macros.md
@@ -35,12 +35,13 @@ macro), use the constant [PACKAGE_NAME](lib/globals.html#PACKAGE_NAME).
 
 ## Debugging
 
-* `bazel query --output=build //my/path:all` will show you how the BUILD
-file looks like after evaluation. All macros, globs, loops are expanded.
+*   `bazel query --output=build //my/path:all` will show you how the BUILD file
+    looks like after evaluation. All macros, globs, loops are expanded.
 
-* You can also use [print](lib/globals.html#print) for debugging. It displays
-the message as a warning during the loading phase. Except in rare cases, remove
-your `print` calls before submitting the code to the depot.
+*   You can also use [print](lib/globals.html#print) for debugging. It displays
+    the message as a warning during the loading phase. Except in rare cases,
+    either remove `print` calls, or make them conditional under a `debugging`
+    parameter that defaults to `False` before submitting the code to the depot.
 
 ## Errors