Live data from Hacker News

GitHub CLI now collects pseudoanonymous telemetry

cli.github.com

31–40 of 368 posts

Re: GitHub CLI now collects pseudoanonymous telemetry

#31

can someone explain why github has a CLI? why wouldn't you just use git?

gh is insanely powerful, especially if you let your coding agent use it. It’s one of my top tools. Gh lets you use GitHub features such as issues, pull request, reading CI pipelines, creating CI pipelines, etc. git is just for code version control.

Re: GitHub CLI now collects pseudoanonymous telemetry

#34
post #26

So happy I deployed gitea to my homelab last month. It's got an import feature from github and honestly just faster and better uptime that github. Claude can use it just fine with tea cli and git. It's pretty much a knockoff github, but I think it's better so far.

I’m running Forgejo which has the same core code and yeah it’s amazing. Faster and better uptime indeed. It even works when my internet goes down because it’s on a Pi 4 here in the cabinet next to my desk Backups are done with borg and syncthing to offsite location. It takes a bit of work setting it up but after that maintenance time is near zero. I just manually SSH in once every two weeks to check SSD space, RAM usage and run apt update and upgrade, and major version bumps

Re: GitHub CLI now collects pseudoanonymous telemetry

#35

can someone explain why github has a CLI? why wouldn't you just use git?

My last job they used gh features heavily - pull requests, issues, and gha most of all. So having the cli made automating (or interacting with agents) github-specific tasks possible.

Re: GitHub CLI now collects pseudoanonymous telemetry

#37
post #14

Why we collect telemetry ...our team needs visibility into how features are being used in practice. We use this data to prioritize our work and evaluate whether features are meeting real user needs. I'm curious why corporate development teams always feel the need to spy on their users? Is it not sufficient to employ good engineering and design practices? Git has served us well for 20+ years without detailed analytics…

> I'm curious why corporate development teams always feel the need to spy on their users?

I've repeatedly talked about this on HN; I call it Marketing Driven Development. It's when some Marketing manager goes to your IT manager and starts asking for things that no customer wants or needs, so they can track if their initiatives justify their job, aka are they bringing in more people to x feature?

Honestly, with something as sensitive as software developer tools, I think any sort of telemetry should ALWAYS be off by default.

Re: GitHub CLI now collects pseudoanonymous telemetry

#39

Love it when a PR is brief: https://github.com/cli/cli/pull/13254 > Removes the env var that gates telemetry, so it will be on by default.

Not only on by default, it also isn't possible to disable it seems. It's forced on (other than enterprise it seems)
Post reply on HN