Repository navigation
Clarify that DO_NOT_TRACK only disables telemetry if 1 or true #45957
Description
Activity
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
@hashcatHitman Thanks for opening an issue! I'll get this triaged for the team to take a look.
Reacted by Sam KellamWe're not accepting contributions for this at this time, as we need to establish whether this is the right repo/place for investigation first. Once we've established that we'll clarify whether the community can contribute, but until then I'm going to lock conversation on this issue.
- locked and limited conversation to collaborators
on Sep 22, 2026 - added a commit that references this issue
on Sep 28, 2026
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/github-cli/github-cli/github-cli-telemetry#how-to-opt-out
What part(s) of the article would you like to see updated?
The section on environment variables currently looks like this:
Saying that any falsy value works for
GH_TELEMETRYright before introducingDO_NOT_TRACKcan create the implication that any truthy value would be accepted forDO_NOT_TRACK. I believe this is not the case though; it looks likeDO_NOT_TRACKmust be1ortrue. It would be nice to clarify this.It also seems like most people set
DO_NOT_TRACKto1anyway, so it would be good to be explicit for the opposite reason too; we don't want people to assume that onlytrueis accepted.Additional information
No response