AI
A Century of Innovation, a Decade of Fragmented Tooling
GM introduced the electric starter in 1912. Super Cruise debuted on the Cadillac CT6 in 2017. The company has moved fast on hardware for over a century. Software was different.
Over a decade ago, GM stopped relying on external vendors and insourced all development tools. The result was still fragmented: inconsistent tooling across teams, limited visibility, slow iteration cycles, and unclear ownership. Duplication of effort compounded the risk. The problem was not that GM lacked tools. It had too many, with no coherent standard tying them together.
Choosing GitHub and Setting the Target State
Mario Parisi and his team interviewed developers and CIOs, attended tech forums, and met with Microsoft to study what top clients do and avoid. The target state was specific: one SaaS-based source control system, consistent pipeline execution, security integrated early in the lifecycle, and dashboards that give real-time visibility into development health.
GitHub won because it offered full-stack capabilities with governance built in from the start, not bolted on later. The goal was the best possible developer experience for 20,000 engineers.
Migrating 170,000 Repositories Without Stopping Production
With 20,000 developers moving to a new platform, skepticism was the default. Developers wanted to stay in ADO, Bitbucket, or Jenkins. Kyle Willard’s team turned that resistance by making skeptics into champions of change, not forcing compliance.
“The migration to the GitHub platform wasn’t just a tooling upgrade, it was a full cultural shift.” — Kyle Willard
The scale was 170,000 repositories and 32,000 pipelines. Instead of a bulk cutover, the team scheduled, tracked, and automated each migration with zero disruption to ongoing work. Clear ownership followed: every repository now has a defined owner, and nobody asks “who fixes this pipeline?” anymore.
VNet Injected Runners and the Metrics That Followed
VNet injected runners are GitHub-hosted machines injected into GM’s network. They inherit firewall rules from data centers and manufacturing plants and start with a clean slate every run. One developer’s corrupted build tool no longer breaks the next developer’s build.
Post-migration numbers: 94% increase in pipeline reliability, 50% average build time reduction, 10,700 vulnerabilities remediated, 22,000 exposed secrets resolved, and 39,000 Copilot users. The road ahead adds AI to automate repetitive tasks and catch compliance gaps before production.
Notable Quotes
The migration to the GitHub platform wasn’t just a tooling upgrade, it was a full cultural shift. Kyle Willard · ▶ 7:13
failure was not an option for us Kyle Willard · ▶ 7:22
we were able to resolve 22,000 exposed repository secrets Kyle Willard · ▶ 9:24
Key Takeaways
- Insourcing tools without unifying them leaves teams with 170,000 repos on incompatible pipelines.
- Scheduled, automated migrations with zero downtime converted skeptics into platform advocates.
- VNet injected runners give GitHub-hosted machines GM’s firewall rules and a clean slate every build.