When Microsoft bought GitHub in 2018, the deal felt like a marriage with a carefully written prenup: Microsoft would own the world’s largest code repository, and GitHub would keep its developer-first soul. For years, that arrangement mostly worked. GitHub ran as a quasi-independent island, and Microsoft seemed happy to stay in the background, letting the platform’s community-minded culture thrive. Then, in August 2025, the ground shifted. Microsoft moved GitHub into its CoreAI division, and GitHub CEO Thomas Dohmke announced he would leave at the end of the year. For many developers, it felt like the end of an era—and not in a good way. The old fear resurfaced with a vengeance: GitHub would become just another arm of Microsoft, its open-source friendliness flattened by corporate process, its independent spirit swallowed by the mothership. Into this delicate moment steps Kyle Daigle, a 13-year GitHub veteran who has been one of the loudest voices insisting that GitHub should stay GitHub. His new role makes him not only GitHub’s chief operating officer but also Microsoft’s chief marketing officer of developer, responsible for developer marketing across the entire company. That dual mandate is a signal in itself. Microsoft isn’t trying to absorb GitHub so much as it’s trying to export the best of GitHub into everything else it does. Daigle knows the fear because he has lived it. He has seen GitHub evolve from a startup into a Microsoft property, and he understands why developers worry that integration means homogenization. But he argues that the old goal of “don’t break GitHub” is no longer enough. The real goal, he says, is to take GitHub’s community-first DNA and let it influence Microsoft’s developer tools, marketing, and culture. That is a much more ambitious bet—and it explains why Microsoft put someone from GitHub in charge of its overall developer narrative. It says that the best way to make Microsoft developer-friendly is to let the people who built the most developer-friendly platform in the world show everyone else how it’s done.
Daigle’s job, as he describes it, is less about protecting GitHub from Microsoft and more about bringing two worlds together in a way that makes both stronger. “Bringing teams together—engineering teams and marketing teams and everyone that wasn’t talking to each other before—has been a really big part of the work,” he said. He sees opportunities for GitHub to directly help and impact the overall mission of Microsoft, rather than remaining cloistered in a way that doesn’t serve either GitHub’s mission or Microsoft’s mission. That is a striking shift in tone. For years, the unofficial mantra inside GitHub was to preserve its distinct identity, to keep the corporate parent at arm’s length. Now Daigle is talking about breaking down barriers between developer teams across Microsoft while making sure not to leave any key legacy Microsoft developer products behind. It’s a delicate balance, and he acknowledges that GitHub’s relationship with Microsoft has changed since the end of the standalone CEO era. But the change, he insists, is for the better. Developer teams across Microsoft and GitHub are now sharing foundations and the GitHub Copilot software development kit across organizations “in a way that would have seemed improbable before.” That kind of collaboration would have been unthinkable when GitHub was still trying to prove it could remain independent inside Microsoft. Now it’s becoming routine. Daigle’s key takeaway from all this work is simple: “We’ve always been a platform, not just a product. We need developers to build with us and on us.” That platform mindset is exactly what Microsoft needs as it tries to connect its sprawling product portfolio. As Microsoft historians know, and as Daigle likes to point out, Microsoft’s challenge isn’t creating products—it’s connecting them. GitHub, with its vast community and its developer-first ethos, can be the connective tissue.
The integration hasn’t been without growing pains. The rise of AI agents has strained GitHub’s infrastructure in ways that the platform was never designed to handle. Over the past few months, GitHub has experienced some significant outages, including one in August that lasted nearly eight hours. For developers who rely on GitHub to run their businesses and their open-source projects, those outages were more than an inconvenience—they were a reminder that the platform’s success has created enormous technical pressure. GitHub officials have said they are migrating from their own datacenters to Azure to try to ease some of the capacity issues, but Daigle is quick to point out that this is not a simple lift-and-shift process. It’s a major re-architecture of the platform. As of early October, GitHub was roughly 60% through its Azure migration, and the work is being done carefully, with an eye toward avoiding the kinds of bottlenecks that have caused recent problems. One of the key challenges is separating compute and storage for the Git distributed version control system, so that developers and agents working concurrently in the same repositories don’t overwhelm the system. The scale of the problem is almost hard to fathom: developers and agents made 7.38 billion commits on GitHub in September alone. That kind of volume would have been unmanageable without Microsoft’s scaling expertise and Azure support. Daigle says GitHub is in a unique position because it can request major additional capacity—like millions of CPUs—and work with Microsoft teams to provision it. That kind of access is a benefit of being part of the mothership, even if it comes with the cultural anxieties that have accompanied the integration. The outages may have shaken some confidence, but Daigle sees them as a necessary part of a transition that will ultimately make GitHub more resilient and more capable of handling the agent-driven future.
That future is already arriving. GitHub is no longer just a platform for source control and collaboration; it is becoming “the store for anything that needs to be coded and needs some verification,” in Daigle’s words. In the new world order, GitHub isn’t just the store for apps—it’s increasingly the store for agents. That means GitHub is acting as the developer layer for Microsoft’s “agent factory” strategy, helping customers create agents at scale. Microsoft co-founder Bill Gates once envisioned Microsoft as a “software factory” that could produce software at scale. Today, CEO Satya Nadella and his team talk about Microsoft as an “agent factory,” and GitHub is central to that vision. GitHub currently serves more than 200 million developers, plus an unknown but quickly growing number of AI agents. That growth presents a fundamental challenge: developers need to think in new ways when it comes to agents. They need to consider scaling APIs for agents separately from humans, creating APIs designed specifically for agents, rewriting documentation and tooling so agents can consume GitHub efficiently, and treating agent access as a fundamentally different workload from human access. It’s not just about making the existing platform work for bots; it’s about redesigning the platform for a world where software is built by a mix of humans and machines. Daigle believes that in the longer term, AI will make software economically viable for smaller audiences—a family, an individual, or a single team. The app-store model may change substantially in the coming years, as people create highly specialized applications for narrow use cases. GitHub could help like-minded users discover software for specific interests, such as a household or community use case. That vision is both exciting and a little unsettling, but Daigle embraces it. He sees a future where professional developers and newer builders can create and run software and agents without needing to manage token costs, uptime, monitoring, or operational overhead. The platform would handle all of that behind the scenes, letting people focus on building things that matter to them.
For all the talk of agents and infrastructure, Daigle’s message is ultimately about trust. GitHub has been a home for developers for nearly two decades, and it has weathered ownership changes, controversies, and now the AI revolution. The integration with Microsoft could have been a disaster, a cautionary tale about corporate acquisition swallowing a beloved community. Instead, Daigle argues, it’s an opportunity to spread GitHub’s values across one of the largest technology companies in the world. The fact that Microsoft chose to consolidate its developer-facing messaging and community outreach under someone who came from GitHub, not from its traditional developer division, gives weight to that argument. Daigle is not a Microsoft lifer trying to impose a corporate agenda; he’s a GitHub lifer who believes that the platform’s community-driven approach can transform Microsoft from the inside. That doesn’t mean every developer is convinced. The recent outages, the organizational changes, and the departure of Dohmke have all fueled skepticism. But Daigle seems to understand that trust is earned through action, not promises. He points to the sharing of foundations and Copilot SDKs as evidence that the integration is producing real results, not just internal PowerPoint decks. He talks about breaking down barriers between developer teams, not building new ones. And he emphasizes that GitHub’s mission—to help developers build software together—remains unchanged, even as the platform’s role evolves.
Looking ahead, GitHub has more to say at its Universe conference in San Francisco on October 28-29. Daigle promises the event won’t focus on code generation alone. It will include information on tools covering the full lifecycle, proactive security approaches, and how to determine whether software is working well after deployment. That is a much broader vision than the GitHub of old, which was primarily about hosting code and managing projects. Now GitHub is positioning itself as a platform that supports developers from the first line of code to the moment software is running in production, and beyond. “We’re looking to solve the core parts of the platform, like Git, like Actions, in a way that I hope will make people excited and feel like they can absolutely trust GitHub for the next decade to come,” Daigle said. That is the heart of his message: change is happening, but it’s happening in service of the developer community. The integration with Microsoft, the Azure migration, the focus on agents—all of it is aimed at making GitHub more reliable, more scalable, and more useful for the people and machines that depend on it. Daigle wants developers to feel like GitHub is still their home, even as it grows into something bigger. He wants them to believe that the platform’s soul is intact, and that Microsoft’s involvement will make it stronger, not less independent. Whether he succeeds will depend on the next few years of execution, but his optimism is grounded in a simple conviction: GitHub’s community-first ethos is worth protecting, and it’s also worth sharing. In the Microsoft 2.5 era, that might be the most important thing of all.
