GitHub vs Airtop

Two moves on July 30 define GitHub's current position. It retired GitHub Models entirely — playground, model catalog, inference API, and bring-your-own-key, with no customer exempt — and put stacked pull requests into public preview. Everything else in the batch is Copilot: monthly roll-ups for Visual Studio and VS Code, agent skills and MCP reaching general availability in code review, and a run of enterprise controls covering device restrictions, default model enablement, and usage attribution.

GitHub is narrowing where it competes and widening where it governs. Exiting model serving concedes that layer rather than defending a catalog against dedicated inference providers, while the Copilot work moves up the stack into agents, skills, and MCP — the parts tied to the repository rather than to the weights. Meanwhile the core collaboration product is getting attention it had not received in years: stacked pull requests address the large-change review problem directly, and the self-repository action syntax cleans up a long-standing Actions annoyance. The enterprise stream running underneath all of it is consistent: admins get device-level, model-level, and reporting-level control as agents gain the ability to act.

Expect stacked pull requests to move from preview toward general availability and the agent-governance controls to keep expanding, since every recent Copilot capability has shipped with an admin policy attached. What GitHub recommends to teams that were relying on the retired inference API is not addressed in these entries.