When Microsoft announced its $7.5 billion acquisition of GitHub in 2018, developers expressed a mix of skepticism and cautious optimism. The open-source community feared Microsoft's corporate influence, while others hoped for stability and resources. Nearly eight years later, the platform is in turmoil. GitHub now confronts a fight for its very survival amid a surge of outages, security vulnerabilities, and a talent drain that threatens its position as the world's leading code hosting service.

The root of the crisis

The current struggles can be traced back to the summer of 2025, when former GitHub CEO Thomas Dohmke resigned. Microsoft did not replace him, instead folding GitHub's leadership into the CoreAI team led by Jay Parikh, a former Meta engineering chief personally recruited by Satya Nadella. Parikh's decision to leave the CEO position vacant has created a leadership vacuum. GitHub employees—known as Hubbers—who valued the platform's independent culture now report directly to Microsoft's AI division, causing friction and uncertainty.

Parikh is reportedly unpopular among Microsoft staff. His approach has been criticized for lacking empathy and failing to understand GitHub's unique community-driven ethos. The reorganization has blurred lines between GitHub and Microsoft's Developer Division, with revenue now reporting into Microsoft Customer and Partner Solutions (MCAPS) and product work split across teams. One employee lamented, "There's basically no more GitHub at all anymore. It's all Microsoft."

Talent exodus accelerates

Since Dohmke's departure, a steady stream of senior leaders and engineers have left GitHub. Many followed Dohmke to his new startup, Entire, a developer platform that directly competes with GitHub. Of the 30 employees listed at Entire, at least 11 are former Hubbers. This brain drain includes veteran executives like Julia Liuson, who oversaw GitHub revenue and engineering for 34 years at Microsoft before retiring in April 2026. Jared Palmer, who joined GitHub as senior vice president in October 2025, announced his departure after just six months to become VP of engineering at Xbox. Elizabeth Pemmerl, GitHub's chief revenue officer, also resigned in April, replaced by Dan Stein from MCAPS.

The leadership vacuum has left teams directionless. According to sources, middle managers are scrambling to fill gaps, but morale is low. Hubbers report that the once-strong sense of mission has evaporated, replaced by bureaucratic Microsoft processes and a relentless focus on AI integration rather than core infrastructure reliability.

Outages and security failures

Technical issues have compounded the leadership woes. Over the past year, GitHub has experienced multiple major outages, some lasting hours and disrupting millions of developers worldwide. The most recent incidents forced CTO Vladimir Fedorov to issue a public apology. He admitted that GitHub's infrastructure has struggled to keep pace with a massive growth spike in pull requests, commits, and new repositories. The platform's ongoing migration to Azure servers—a project Fedorov initiated—has introduced additional complexity, particularly with MySQL clusters, leading to further instability.

Security breaches have also damaged GitHub's reputation. In March 2026, Wiz Research used AI models to uncover a critical vulnerability in GitHub's internal git infrastructure that could have allowed attackers to access millions of public and private code repositories. The team patched it within six hours, but the incident exposed underlying weaknesses. Worse, in May 2026, an employee installed a malicious VS Code extension, leading to the breach of 3,800 internal code repositories. One Microsoft employee noted that VS Code frequently prompts users to install new extensions, some of which have been pulled from the marketplace after infecting users with cryptomining tools. The incident highlights systemic security flaws in the developer ecosystem that GitHub is meant to protect.

Competition intensifies

While GitHub struggles internally, competitors are gaining ground. Parikh has privately warned colleagues that the platform faces a "critical threat" from rivals like Cursor and Claude Code, both of which have surpassed GitHub Copilot's AI coding capabilities. Microsoft reportedly considered acquiring Cursor in recent months to close the gap, but no deal materialized. In an effort to boost Copilot's quality, Microsoft canceled many of its own Claude Code licenses, forcing internal developers to rely on GitHub's AI tool—a move that has generated resentment.

The rise of Entire, led by Dohmke, also poses a direct challenge. With a lean startup culture and deep understanding of developer needs, Entire could lure away users frustrated by GitHub's instability. Meanwhile, influential developers like Mitchell Hashimoto, creator of the Ghostty terminal, publicly announced they are leaving GitHub, citing daily failures and a loss of trust. Hashimoto wrote, "GitHub is failing me, every single day, and it is personal. I want it to be better, but I also want to code. And I can't code with GitHub anymore."

Pricing backlash and AI monetization

GitHub's attempt to monetize its Copilot AI tool has sparked further outrage. Starting next month, every Copilot plan will include a monthly allotment of "GitHub AI credits." Once users exceed their limit, they will be cut off unless they purchase additional credits. Previously, GitHub gracefully downgraded users to a less capable AI model, allowing experimentation without fear of interruption. The new usage-based billing system has angered developers who view it as a cash grab at a time when the platform's reliability is crumbling.

The backlash comes as Microsoft pushes deeper into AI across its product portfolio. But the rush to integrate Copilot into GitHub has diverted resources from fundamental improvements. CTO Fedorov has stated, "Our priorities are clear: availability first, then capacity, then new features." Yet many observers note that little has changed since that promise. Developers continue to complain about slow load times, failed merges, and unresponsive dashboards.

Broader Microsoft upheaval

GitHub's crisis is part of a larger upheaval within Microsoft. The CoreAI team under Parikh has seen multiple defections to Xbox, where new CEO Asha Sharma is building her own leadership team. Xbox has hired several former CoreAI executives, including Jared Palmer and Scott Van Vliet, the latter now serving as Xbox CTO. This internal brain drain suggests that even Microsoft employees are eager to escape Parikh's leadership.

Other recent changes include Microsoft retiring Teams' Together Mode, rebranding Xbox to all caps, and testing a resizable taskbar for Windows 11. The company also said goodbye to S. "Soma" Somasegar, its former Developer Division chief who passed away at 59, leaving a void in the developer community that Nadella called "very personal." These shifts reflect a company in transition, but GitHub's unique challenges require urgent, focused attention.

GitHub holds a special place in the hearts of millions of developers who rely on it daily for code collaboration, open-source projects, and CI/CD pipelines. Its decline would have ripple effects across the entire software industry. Competitors like GitLab and Bitbucket stand ready to absorb disaffected users, while startups like Entire and Cursor offer modern alternatives. The pressure is now on Parikh and Microsoft's CoreAI team to stabilize GitHub, restore trust, and fend off rivals before it's too late. If they fail, Microsoft risks losing the developer ecosystem that helped transform it from a software vendor into a cloud and AI powerhouse.

Source: The Verge News