GitHub GHES 到 GHEC DR 企业在线迁移功能 GA
Enterprise Live Migrations from GHES to ghe.com generally available
核心托管平台推出重大能力跃迁：支持从本地服务器到云端的零停机迁移。对于拥有大型活跃仓库且无法接受长时间停机的团队，这是关键的架构升级选项，建议评估迁移路径。
Enterprise Live Migrations (ELM) is now generally available, enabling near-zero-downtime repository migrations from GitHub Enterprise Server (GHES) to GitHub Enterprise Cloud with Data Residency (GHEC DR), so you can move even your largest, most active repositories while the contributions keep flowing.
企业实时迁移（ELM）现已全面可用，支持从 GitHub Enterprise Server (GHES) 到具有数据驻留功能的 GitHub Enterprise Cloud (GHEC DR) 的近乎零停机时间的仓库迁移，因此即使在你最大的、最活跃的仓库中，在贡献持续进行的同时也能完成迁移。
Key features of ELM to consider when selecting a tool for your next repository migration are:
在选择用于下一次仓库迁移的工具时，需要考虑 ELM 的关键功能包括：
- Cutover in minutes, not days: ELM continuously syncs data from source to target, so developers keep working in their repositories throughout the migration. When you’re ready, the cutover only requires the time to drain remaining in-flight changes. This is especially valuable for business-critical repositories contributed to by geographically dispersed teams where there is no convenient downtime window to fit a migration into.
- Built for the largest monorepos: ELM was purpose-built to handle the repositories that push existing tooling to its limits (i.e., massive monorepos with deep git history, large volumes of issues and pull requests, and constant activity around the clock). Resource-level progress tracking surfaces failures before cutover, so you can make an informed decision about when to proceed.
- Use ELM alongside GitHub Enterprise Importer (GEI): ELM complements GEI, giving you flexibility to choose the right tool for each repository based on its size, shape, and activity. Use GEI for straightforward migrations where brief downtime is acceptable, and ELM for the repositories that need a zero-disruption approach. Run them concurrently as part of the same migration strategy.
- Manage migrations with the gh elm extension: Install the GitHub CLI extension to configure credentials and manage the ELM lifecycle — from creating and monitoring a migration to initiating cutover — through the GHES REST API. Human-readable output helps you track progress, while JSON output supports scripting and automation.
- 分钟级切换，而非天级：ELM 持续将数据从源同步到目标，因此在整个迁移过程中开发人员可以继续在其仓库中工作。当你准备好后，切换仅需花费排空剩余进行中更改的时间。这对于由地理上分散的团队贡献的业务关键型仓库尤其有价值，因为这些仓库没有方便的停机窗口来安排迁移。
- 专为大型单体仓库构建：ELM 是专门设计来处理那些使现有工具达到极限的仓库（即具有深层 git 历史、大量问题和拉取请求以及全天候持续活动的庞大单体仓库）。资源级别的进度跟踪可在切换前暴露失败情况，以便你做出是否继续进行的明智决策。
- 与 GitHub Enterprise Importer (GEI) 配合使用 ELM：ELM 补充了 GEI，让你能够根据每个仓库的大小、结构和活动情况选择最适合的工具。对于短暂停机可接受的简单迁移使用 GEI，而对于需要零中断方法的仓库则使用 ELM。作为同一迁移策略的一部分同时运行它们。
- 通过 gh elm 扩展管理迁移：安装 GitHub CLI 扩展以配置凭据并管理 ELM 生命周期——从创建和监控迁移到发起切换——通过 GHES REST API。人类可读的输出帮助你跟踪进度，而 JSON 输出支持脚本编写和自动化。
ELM runs as a service on your GHES appliance, driven by the gh elm CLI. ELM supports migrations from GHES versions 3.17.18+, 3.18.12+, 3.19.9+, 3.20.3+, 3.21.3+, and 3.22.0+. This release ships with the most recent GHES patch releases, with plans to expand to additional migration paths.
ELM 在你的 GHES 设备上作为服务运行，由 gh elm CLI 驱动。ELM 支持从 GHES 版本 3.17.18+、3.18.12+、3.19.9+、3.20.3+、3.21.3+ 和 3.22.0+ 进行迁移。本次发布附带最新的 GHES 补丁版本，并计划扩展到更多的迁移路径。
To get started, check out the Enterprise Live Migrations documentation.
要开始使用，请查看企业实时迁移文档。
The post Enterprise Live Migrations from GHES to ghe.com generally available appeared first on The GitHub Blog.
来自 GHES 到 ghe.com 的企业实时迁移全面可用的文章首先出现在 GitHub 博客上。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力