Who owns GitHub?

Microsoft owns GitHub. The acquisition closed in 2018, after GitHub operated as an independent company for a decade following its founding in 2008.

How the acquisition changed things, and how it did not

GitHub has continued to operate with its own branding, its own product decisions, and its own leadership rather than being absorbed directly into Microsoft’s existing developer tools. Core behavior that developers rely on daily, public repositories, issues, pull requests, the general workflow, has stayed consistent since the acquisition.

What did change: GitHub gained deeper integration with other Microsoft-owned tools over time, most notably Visual Studio Code, and unlimited private repositories became available on the free tier not long after the deal closed, a meaningful shift from GitHub’s earlier free-tier limits.

Some developers were wary of the acquisition at the time, given Microsoft’s historically complicated relationship with open source in earlier decades. In practice, GitHub has remained the dominant place for public open-source code, and Microsoft itself has become one of the most active open-source contributors on the platform.

Why this comes up

Ownership questions like this tend to surface when people are deciding whether to trust a platform with years of their work, which is a reasonable thing to think about before building a public portfolio somewhere. GitHub’s scale, and the fact that migrating away from it is realistically difficult once a project has real history and community activity behind it, means most developers treat it as a safe long-term default despite the corporate ownership.

Using what is already there

Regardless of who owns the platform, a GitHub account with real activity behind it, repositories, languages, a contribution history, is a genuinely useful record of your work. resumefromgit.com turns that record into a visual CV and a downloadable resume PDF, reading only from what GitHub already makes public, with no account or sign-up required on your end.