GitHub CLI now collects pseudoanonymous telemetry (cli.github.com)

Article summary

The GitHub CLI now collects pseudoanonymous telemetry by default, with some users expressing concerns about data collection and privacy. The telemetry can be opted out of in several ways, including setting environment variables or configuring the CLI. Some users are looking for ways to avoid the telemetry or pin their version to avoid it. The change is part of the v2.91.0 release.

Main themes

• telemetry collection
• data privacy
• user consent
• data-driven decision making
• GitHub CLI
• pseudoanonymous data
• EU GDPR regulations
• corporate data collection practices

What commenters say

• Telemetry collection is unnecessary and can be a distraction from good engineering and design practices.
• Data collection can be useful for identifying areas of improvement, but it must be done transparently and with user consent.
• Some companies prioritize data-driven decision making over user intuition and experience.
• Pseudoanonymous telemetry can be easily de-anonymized and may not provide accurate insights.
• Opt-in telemetry collection is preferable to opt-out, especially in light of EU GDPR regulations.
• Users are skeptical of companies' claims of anonymity and transparency in data collection.
• Telemetry can be used to refine interfaces and documentation, but it is not a substitute for observing user behavior.
• Companies may use data collection for purposes beyond improving user experience, such as advertising or analytics.