When Microsoft announced it would buy GitHub in 2018 for roughly seven and a half billion dollars in stock, many developers reacted with dread. GitHub was the home of open source, and Microsoft had spent years as the company open-source advocates loved to distrust. Four years on, the story is less dramatic than the fears: the platform still looks and feels like itself, and the parent company mostly left it alone while quietly building the infrastructure around it.
The fears at the time
Developers worried about three things: that GitHub would be tied tightly to Microsoft products, that prices would rise, and that the culture of the platform would change. Some projects moved to rival hosting services within days of the announcement. Those moves were real but limited, and the exodus did not continue.
What Microsoft actually did
- Kept it independent. GitHub continued as a separate brand, with its own leadership and its own conferences.
- Made core features free. Private repositories for small teams, once a paid feature, became free, widening access for students and individual developers.
- Invested in automation. GitHub Actions turned the site from a place that stores code into one that builds, tests and deploys it.
- Built security tooling. Dependency alerts, secret scanning and code scanning became standard parts of the product.
- Launched Copilot. An AI coding assistant, developed with a partner, arrived as a paid subscription for suggesting code inside editors.
The business logic
For Microsoft, the value of GitHub was never only revenue. It owns the place where developers spend their day, and that influence helps its cloud and tools business. If developers build and deploy from GitHub, the easiest place to run their code is a cloud with good integration. The strategy depends on trust: if the company abused its position, developers could move elsewhere with little notice, because Git itself is portable.
Controversies along the way
It was not entirely smooth. Copilot sparked debate about whether training an AI on public code respected open-source licenses, leading to criticism from some maintainers and legal challenges that were still working through the courts. The platform’s role in takedown requests also drew attention, as did past decisions about restricting access in certain countries due to sanctions. And outages, as with any large service, tested patience.
What it means for developers
- Your code is portable. Keep local clones and mirror important repositories, so a platform change never traps you.
- Watch the license terms. Understand how your code can be used by tools and services, and choose licenses with that in mind.
- Use security features. Free scanning and alerts catch real problems before attackers do.
- Be deliberate about AI tools. Review suggestions as you would a colleague’s pull request.
The competition
Rivals such as GitLab and Bitbucket continue to serve teams that prefer different pricing, self-hosting or integrated pipelines. The open-source world also has smaller hosts and self-run options for those who want to avoid dependence on a single company. Competition has kept GitHub honest on features and price, even if its network effect, the fact that everyone’s projects and contributors are already there, remains a powerful advantage.
Open source maintainers: a mixed picture
Maintainers got free tools, sponsorship programs and better security alerts, but they also inherited more automated noise and more expectations. Many small projects still depend on one or two volunteers, and a platform that makes it easy to open an issue does not make it easier to fix one. Funding programs help at the margins, yet the underlying question of who pays for the software the whole industry depends on remains largely unanswered, and it is one reason the platform’s relationship with its community matters so much.
How to judge the next four years
Look at three signals: whether the free tier stays generous, whether data portability remains simple, and whether new products such as AI assistants are offered with clear controls and opt-outs. If those hold, the promise of independence is real in practice, not just in press releases.
Verdict so far
The apocalypse never arrived, but neither did a golden age of neutrality. GitHub is a bigger, more commercial product than it was in 2018, and its fortunes are tied to the AI strategy of its owner. For most developers, the daily experience improved: more automation, better security and less friction. The sensible response is neither celebration nor panic. Use the platform for what it does well, keep your options open, and remember that trust between developers and platforms is something that has to be earned again every year.
