Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
GitHub announces that starting April 24, it will default to using Copilot user data to train AI models
GitHub recently announced that starting April 24, 2026, it will update its code repository policy to utilize user interaction data for training its AI models. The data collection will include users of Copilot Free, Pro, and Pro+ and will cover model input/output, code snippets, contextual information, repository structure, and chat interaction records.
GitHub’s Chief Product Officer Mario Rodriguez stated that incorporating interaction data aims to improve the accuracy and safety of code suggestions. He also mentioned that pre-testing with internal Microsoft data has significantly increased suggestion acceptance rates. Notably, the policy adopts a “pre-set opt-in” mechanism, meaning affected users must manually go into privacy settings to disable the relevant options to opt out. This has sparked widespread discussion within the developer community regarding the definition of private repositories and data rights.
Currently, Copilot Business, Enterprise users bound by contractual terms, and educational users are not affected by this change. GitHub emphasized that this move aligns with industry practices common among major companies like Anthropic, JetBrains, and Microsoft. However, including private repository code in training datasets essentially challenges traditional notions of “privacy,” even though GitHub claims its goal is to optimize development workflows.
From an industry perspective, as high-quality public domain code data becomes scarce, leading AI companies are accelerating efforts to mine private interaction data and other “deep data” to seek performance gains. This policy shift not only signifies GitHub’s move from an open-source hosting platform toward a closed-loop AI training ecosystem but also indicates that the field of AI developer tools is entering a new stage of data compliance and model evolution competition.