Microsoft is utilizing Amazon Web Services to bolster GitHub's infrastructure as the platform struggles with a massive surge in AI-driven development activity. Although Microsoft originally planned to migrate the entire service to its own Azure cloud by 2027, the current demand for compute resources has outpaced internal capacity. This temporary multicloud approach aims to maintain service availability while the company continues its long-term transition to Azure.

Source

GitHub is transitioning the Copilot extension for JetBrains IDEs to use the Copilot CLI as the default agent harness. This architectural shift replaces the previous local harness to ensure consistency across all GitHub Copilot platforms. The update allows the IDE to start and monitor independent background sessions while leveraging a unified agentic coding framework.

Source

Organization administrators can now manage GitHub Copilot code review settings at scale through new runner type configurations. These controls allow for the enforcement of specific self-hosted or large runners across all repositories within an organization. By locking these settings, administrators ensure that organizational defaults override individual repository configurations for consistent performance and security.

Source

GitHub Copilot CLI has introduced a unified configuration system accessible via the new `/settings` command. This update replaces scattered commands and manual file editing with a single, schema-driven interface for managing tool behavior. Users can now modify preferences through a full-screen interactive dialog, quick inline one-liners, or automated scripts.

Source

GitHub has introduced Agentic Workflows in public preview, allowing for the automation of reasoning-based tasks within GitHub Actions. This feature enables the creation of coding agents that can handle issue triage, analyze CI failures, and update documentation. These workflows are defined using natural language Markdown files which are then compiled into standard Actions YAML.

Source