Back to timeline

Thu, October 2200:00Business/Policy

GitHub migrates 99.99999% of code repository copies to Azure

Decision Brief

What changedGitHub has moved 99.99999% of repository copies to Azure, using per-reference quorums and object storage to complete the remaining migration and scale reads.
Why it mattersThe migration shifts read load onto object storage that scales independently, but the remaining repositories rely on per-reference quorums to finish, so teams depending on GitHub's read/write path should watch consistency during the transition.
Who should careAll AI builders
Affected stackNo specific stack identified
Source confidenceHigh · Official release / blog / repo

GitHub's engineering blog says it has migrated 99.99999% of repository copies to Azure. The remainder will be migrated via per-reference quorums; object storage also lets reads scale independently rather than being tied to the write path. For developers and ops teams relying on GitHub repository hosting, the key change is how reads scale: reads are served by object storage and can be scaled separately. Teams using GitHub as a code host and CI trigger source should watch consistency under the per-reference quorum mechanism while the remaining repositories migrate. The original post did not disclose the migration timeline, specific performance figures, or the size of the remaining repositories.

Summary basis: official / RSS sourceCompiled from the source scope noted above; the original remains authoritative.

Sources

  • GitHub Blog

    Developer workflow, Copilot, CLI, and GitHub platform changes.

  • GitHub Blog

Related intel

留言

登入后即可留言,和其他 builder 交换实测心得。

还没有留言,抢头香。