shaddowie Cone
Tim BrayHere's where you go to tell GitHub that it can’t train CoPilot on your code & interactions: https://github.com/settings/copilot/features
Just sayin’
Jan D@timbray link that scrolls the setting in question at the top of the view: https://github.com/settings/copilot/features#copilot-telemetry-policy
soc
furicle@timbray this link has documentation on what is likely a more comprehensive solution...
spinnyspinlock@timbray I was curious about this yesterday, a friend confirmed the new default (for new accounts) is enabled. I assume it's hoping to catch future users off guard.
I don't believe they will respect the toggle in the future anyway
andyc@timbray Alternatively - https://codeberg.org/
Stu@timbray I no longer have code in Github, but turned off those settings anyway. Hopefully, someone at Redmond is keeping track of the number of people who do.
(because some people like to keep their account to interact with important projects who remain on Github, for the "delete your account" sorts).
Larry Garfield@timbray Where is the "and delete any historical usage of it from before you got around to asking my permission you greedy thieving bastards" button?
"Mutant Rob" Robert Rothenberg@timbray If you disable it for your account, does it disable it for all forks of your code?
Sieva 🚴🚇🏙️🌹@timbray If you're a part of an organization that has bought into Copilot Business, you can't do that. 😒
Martin 
:freebsd:
J$
Nicolás Alvarez@timbray I think this toggle is about training Copilot on your use of Copilot. They'll continue to train on your code regardless.
vdq
System Fault@timbray even better option is to leave github, there are plenty of alternatives - gitlab.com, codeberg.org, gitea.com. I left github in 2018 after they fell under micro$oft.
Garret Polk (masked)@timbray Why are these on by default?? I guess GitHub execs don't believe in asking for consent.