GitHub’s Battle for Existence: The Fight Within Microsoft

GitHub, the popular code hosting platform, is currently facing significant challenges that threaten its survival. These challenges include a series of outages, security issues, and competition pressure. The troubles began after Microsoft acquired GitHub for $7.5 billion in 2018, leading to concerns among developers about Microsoft’s control over the platform.

In recent weeks, GitHub has experienced multiple major outages, a remote code execution vulnerability disclosure, and a security breach in its internal code repositories caused by a “poisoned” VS Code extension on an employee’s device. Former and current GitHub employees have reported a lack of leadership and increased pressure from competitors.

The root of GitHub’s current struggles can be traced back to last summer when former CEO Thomas Dohmke resigned, prompting a significant shakeup in the company’s operations under Microsoft’s control. The leadership team at GitHub now reports directly to Microsoft’s CoreAI team, led by former Meta engineering chief Jay Parikh, who was recruited by Microsoft CEO Satya Nadella to assist with the company’s AI transformation.

Since Dohmke’s departure, GitHub has experienced a talent drain, with some employees following him to his new startup, Entire, which is positioned to compete directly with GitHub. Additionally, GitHub is facing competition from Cursor and Claude Code, with GitHub Copilot falling behind rivals in the AI coding space. Microsoft has considered acquiring Cursor to bridge the gap in GitHub Copilot’s capabilities.

The leadership shakeups at GitHub have continued, with key executives like Julia Liuson and Jared Palmer departing for other roles within Microsoft. These departures, along with the shift in revenue reporting and product work within Microsoft, have left some GitHub employees feeling that the company’s leadership team is no longer effective.

GitHub’s ongoing migration to Azure servers, led by CTO Vladimir Fedorov, has also contributed to the platform’s recent outages. Despite efforts to address data center capacity issues, GitHub has struggled with the increased workload and growth in pull requests, commits, and new repositories.

In addition to the outages, GitHub is grappling with security concerns, including a critical vulnerability that was quickly patched in March and a recent breach of internal code repositories due to a malicious VS Code extension. The platform is also facing backlash over its move to usage-based billing for GitHub Copilot, with users now required to purchase additional AI credits for continued use.

As GitHub navigates these challenges, the pressure is on Parikh and the CoreAI leadership team to secure the platform’s future. Competitors are vying to capitalize on Microsoft’s struggles and potentially attract developers away from GitHub. The outcome of these challenges will determine GitHub’s ability to retain its position in the developer community and maintain its reputation as a leading code hosting platform.