The company presents the work as part of its effort to build Git infrastructure for “agent-scale” demand.
The remaining fraction consists of its busiest repositories. GitHub says it introduced a new write path for those repositories so that cross-region round trips do not cap throughput. It also says the architecture enables stateless replicas backed by Azure Blob Storage.
This is an internal infrastructure change, not a new GitHub product, Git protocol revision, or separately described customer setting. The source does not state an absolute repository count, traffic volume, migration cost, or before-and-after latency and throughput measurements. It also does not give a completion date or establish the effect of the migration on an individual repository, developer, or GitHub customer.