GitHub Is Acquired by Microsoft

Microsoft announced the acquisition of GitHub on June 4, 2018 for $7.5 billion in Microsoft stock — the largest acquisition in Microsoft’s history at the time, surpassing the $2.5 billion paid for Minecraft’s developer Mojang in 2014. The deal closed October 26, 2018. GitHub CEO Chris Wanstrath, who had co-founded the company with Tom Preston-Werner and P.J. Hyett in 2008, stepped down; Nat Friedman (previously CEO of Xamarin, itself acquired by Microsoft in 2016) was appointed GitHub CEO.

By June 2018, GitHub hosted over 85 million repositories from more than 28 million developers, including the Linux kernel, the CPython interpreter, the Go programming language, and virtually every major open-source framework. Its pull-request model, code review interface, issue tracker, and GitHub Actions (CI/CD workflows, announced October 2018, launched November 2019) had become the default collaboration layer for software development. GitHub had been profitable for several years before the acquisition and was reportedly generating around $300 million in annual recurring revenue — primarily from GitHub Enterprise, the self-hosted version used by large corporations.

Developer reaction was initially skeptical: Microsoft’s 2000s-era reputation for hostility toward open source and Linux (“the cancer of intellectual property,” then-CEO Steve Ballmer had said in 2001) prompted concern that the company would commercialize or restrict GitHub. Satya Nadella, CEO since 2014, had shifted Microsoft toward open-source contribution — Microsoft had become GitHub’s largest open-source contributor by 2017 and had acquired the .NET Foundation, TypeScript, and VS Code development under the open-source umbrella. GitHub continued operating independently, and Microsoft expanded it with GitHub Copilot (AI code completion, launched June 2021 using OpenAI Codex) and GitHub Copilot Enterprise, which became one of the fastest-growing products in Microsoft’s history by revenue growth rate.

Why This Moment Mattered

The topic is useful because it captures a broader shift in how people build, use, and understand technology. In the short term, it gave users and developers something concrete to react to. In the longer term, it became part of a larger pattern in technology, computing-history, history: hardware, software, services, and user expectations were all changing at the same time.

A good technology milestone usually matters for more than one audience. Enthusiasts notice the specifications or the interface first. Developers ask what new assumptions they can make. Companies look at cost, compatibility, and strategy. Ordinary users mostly notice whether the result makes their devices faster, easier, safer, or more useful.

The Broader Context

This period of computing was shaped by several overlapping transitions: faster networks, more capable mobile devices, cloud infrastructure, stronger security expectations, and software that changed continuously after release. Against that background, the milestone was not an isolated headline. It was one piece of a much larger movement away from static products and toward connected platforms.

That context helps explain why some announcements that looked modest at the time became important later. A browser feature, processor change, development tool, or platform policy can alter what future products are able to assume. Once enough users, developers, and vendors adapt, the new assumption becomes normal.

Looking Back

The value of revisiting the moment is that it shows how technology history is built from many medium-sized steps. Some are celebrated immediately, while others become meaningful only after the ecosystem catches up.

Looking back also keeps the story balanced. Progress usually brings tradeoffs: performance against power use, openness against consistency, convenience against control, and speed against stability. The most interesting milestones are the ones that reveal those tradeoffs clearly. This one belongs in that category because it helps explain not just what changed, but why the direction of computing kept moving the way it did.