From c936cd129b1c9212c15a85bbb771d60e46093b44 Mon Sep 17 00:00:00 2001
From: Daniel <198354403+BaconMan1168@users.noreply.github.com>
Date: Mon, 21 Sep 2026 18:28:56 +0800
Subject: [PATCH] docs: clarify DO_NOT_TRACK values for GitHub CLI telemetry
 opt-out

DO_NOT_TRACK only disables telemetry when set to 1 or true, unlike GH_TELEMETRY which accepts any falsy value.
---
 content/github-cli/github-cli/github-cli-telemetry.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/github-cli/github-cli/github-cli-telemetry.md b/content/github-cli/github-cli/github-cli-telemetry.md
index 1614eacce650..bc7cdc293ae0 100644
--- a/content/github-cli/github-cli/github-cli-telemetry.md
+++ b/content/github-cli/github-cli/github-cli-telemetry.md
@@ -105,7 +105,7 @@ You can opt out of the telemetry you see in the `log` mode described above using
 export GH_TELEMETRY=false
 ```
 
-Any falsy value works: `0`, `false`, `disabled`, or an empty string. You can also use the `DO_NOT_TRACK` convention:
+Any falsy value works: `0`, `false`, `disabled`, or an empty string. You can also use the `DO_NOT_TRACK` convention. Unlike `GH_TELEMETRY`, `DO_NOT_TRACK` only disables telemetry when set to `1` or `true`. Other values, such as `yes` or `enabled`, have no effect.
 
 ```shell
 export DO_NOT_TRACK=true