Patch release notes for GitHub Enterprise Server (#61095)

Co-authored-by: Release-Controller <releasecontroller@github.com>
Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Chris Rose <offbyone@github.com>
Co-authored-by: Laura Coursen <lecoursen@github.com>
Co-authored-by: John Clement <70238417+jclement136@users.noreply.github.com>
Co-authored-by: Pallavi <96553709+pallsama@users.noreply.github.com>
Co-authored-by: isaacmbrown <isaacmbrown@github.com>
Co-authored-by: Devin Dooley <dooleydevin@github.com>

Author: 10 people

content/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities.md

@@ -1287,6 +1287,12 @@ GHE_LICENSE_FILE=/path/license ghe-license import
 # License synchronized.
 ```
 
+## Migrations
+
+### elm
+
+`elm` is the command-line tool for {% data variables.product.prodname_elm %}, a tool for live migrations to {% data variables.enterprise.data_residency_site %}. See [AUTOTITLE](/migrations/elm/elm-cli-reference).
+
 ## Security
 
 ### ghe-find-insecure-git-operations

content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md

@@ -40,7 +40,7 @@ By design, the following features are permanently unavailable on {% data variabl
 | Feature | Details | More information |
 | :- | :- | :- |
 | Features unavailable with {% data variables.product.prodname_emus %} | Because {% data variables.product.prodname_emus %} is the only option for identity management on {% data variables.enterprise.data_residency_site %}, features that are unavailable with {% data variables.product.prodname_emus %} on {% data variables.product.prodname_dotcom_the_website %} are also unavailable on {% data variables.enterprise.data_residency_site %}. Notably, these include gists and public repositories. | [AUTOTITLE](/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts) |
-| {% data variables.product.prodname_importer %} (the "Import repository" button on {% data variables.product.prodname_dotcom_the_website %}) | Instead, the **{% data variables.product.prodname_importer_proper_name %}** is available to migrate data. See [AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer). | [AUTOTITLE](/migrations/importing-source-code/using-github-importer/about-github-importer) |
+| {% data variables.product.prodname_importer %} (the "Import repository" button on {% data variables.product.prodname_dotcom_the_website %}) | This is distinct from **{% data variables.product.prodname_importer_proper_name %}**, which is one of the tools available to migrate data. See [AUTOTITLE](/admin/data-residency/getting-started-with-data-residency-for-github-enterprise-cloud#5-migrate-data). | [AUTOTITLE](/migrations/importing-source-code/using-github-importer/about-github-importer) |
 
 ## Features that work differently
 

content/admin/data-residency/getting-started-with-data-residency-for-github-enterprise-cloud.md

@@ -116,6 +116,7 @@ To migrate existing data to your new enterprise on {% data variables.enterprise.
 Optionally, you can migrate data to {% data variables.enterprise.data_residency_site %} during your trial. However, migrated organizations will count towards the limit of three new organizations during the trial.
 
 * If you're migrating from {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_ghe_server %}, Azure DevOps, or Bitbucket Server, you can migrate source code history and metadata with {% data variables.product.prodname_importer_proper_name %}. See [AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer).
+* For migrations from {% data variables.product.prodname_ghe_server %} 3.17 and later, you can use {% data variables.product.prodname_elm %}. This offers less downtime and better support for complex monorepos. See [AUTOTITLE](/migrations/elm/about-live-migrations).
 * If you're migrating from a different platform, see [AUTOTITLE](/migrations/overview/migration-paths-to-github#migrations-to-ghecom).
 
 ### Example script for {% data variables.product.prodname_importer_proper_name %}

content/admin/monitoring-and-managing-your-instance/multiple-data-disks/configuring-multiple-data-disks.md

@@ -3,15 +3,12 @@ title: Configuring multiple data disks
 product: '{% data variables.product.prodname_ghe_server %}'
 intro: You can configure additional data disks and use them to host data of different services.
 versions:
-  ghes: '>= 3.19'
+  ghes: '>= 3.17'
 contentType: concepts
 category:
   - Scale your instance
 ---
 
-> [!NOTE]
-> The ability to configure and use multiple data disks is in {% data variables.release-phases.public_preview %} and subject to change. We would love to hear your feedback on the preview. You can share it with your customer success team, or leave a comment in the [community discussion post](https://github.com/orgs/community/discussions/181173). Our preferred option is sharing your feedback with your customer success team.
-
 ## Why introduce more disks to the GHES instance?
 
 * Improved resource distribution:

content/migrations/elm/about-live-migrations.md

@@ -0,0 +1,52 @@
+---
+title: About live migrations from GitHub Enterprise Server to GHE.com
+shortTitle: About live migrations
+intro: 'How do live migrations minimize downtime for developers?'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+contentType: concepts
+product: '{% data reusables.elm.ghes-version-requirement %}'
+---
+
+{% data reusables.elm.preview-note %}
+
+## What is {% data variables.product.prodname_elm %}?
+
+{% data variables.product.prodname_elm %} ({% data variables.product.prodname_elm_short %}) is a service for migrating repositories from {% data variables.product.prodname_ghe_server %} to {% data variables.enterprise.data_residency %} ({% data variables.enterprise.data_residency_site %}). It is operated using a command line tool on {% data variables.product.prodname_ghe_server %}.
+
+Migrations are "live" because users can continue using the source repository during most of the migration process. After the repository data is initially collected, webhooks check for changes to the repository, such as new commits or updates to settings. These changes are reported to {% data variables.product.prodname_elm_short %} and included in the migration.
+
+An {% data variables.product.prodname_elm_short %} migration includes a single repository. Organization-level data, such as organization settings, teams, and projects, are **not** included in the migration and must be reconfigured manually on the destination enterprise.
+
+## Differences from {% data variables.product.prodname_importer_proper_name %}
+
+{% data variables.product.prodname_elm_short %} and {% data variables.product.prodname_importer_proper_name %} (GEI) are separate tools that both support migrating repositories from {% data variables.product.prodname_ghe_server %} to {% data variables.enterprise.data_residency_site %}.
+
+The main benefits of {% data variables.product.prodname_elm_short %} are:
+
+* **Reduced developer downtime**: During a migration with GEI, developers lose access to the repository for the duration of the migration. This downtime creates risks like blocked deployments or stalled feature work.
+* **Monorepo support**: {% data variables.product.prodname_elm_short %} is capable of migrating large, complex monorepos with deep histories. These often exceed the capacity of GEI.
+* **Better visibility**: {% data variables.product.prodname_elm_short %} provides detailed repository-level visibility into migration progress, surfacing granular failures so that you can be confident the migrated repository is an accurate replica.
+
+However, because of the higher traffic load associated with live updates, {% data variables.product.prodname_elm_short %} supports fewer concurrent migrations than GEI: {% data reusables.elm.concurrent-migrations %}
+
+You may want to use both tools over the course of a platform migration, prioritizing the repositories that will benefit most from {% data variables.product.prodname_elm_short %}.
+
+## Overview of a migration
+
+Typically, a site administrator runs a migration using the `elm` CLI tool, in a terminal session over SSH. The operator must provide {% data variables.product.pat_generic_plural %} with access to both {% data variables.product.prodname_ghe_server %} and the destination enterprise.
+
+The high-level phases of a migration are:
+
+1. **Creation**: The site admin runs CLI commands to create and start the migration, specifying the source repository and destination.
+1. **Preflight checks**: The migration service verifies parameters, tokens, network connectivity, and repository configuration.
+1. **Backfill**: The {% data variables.product.prodname_elm_short %} tool does an initial crawl to capture all repository data and sends it to the migration service on the destination platform. During the backfill phase, webhooks check for live updates to the repository as the migration continues.
+1. **Cutover**: The source repository is locked and any final live updates are sent to {% data variables.product.prodname_elm_short %}. This is the downtime period for developers.
+1. **Completion**: The migration is finished. The site admin can check the data was migrated successfully.
+1. **Follow-up**: An organization owner performs follow-up tasks on the destination enterprise, such as reconfiguring organization settings and reattributing activity to users.
+
+## Next steps
+
+To get ready to run a migration, see [AUTOTITLE](/migrations/elm/prepare-for-your-migration).

content/migrations/elm/complete-your-migration.md

@@ -0,0 +1,46 @@
+---
+title: Completing your live migration from GitHub Enterprise Server to GHE.com
+shortTitle: Complete your migration
+intro: 'Complete follow-up tasks so users can start using the migrated repository.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+contentType: how-tos
+permissions: 'Organization owners on {% data variables.enterprise.data_residency_site %}'
+---
+
+{% data reusables.elm.preview-note %}
+
+After you have run a migration with the `elm` CLI tool, there are some follow-up tasks to complete.
+
+## Restore users' access
+
+Because {% data variables.product.prodname_ghe_server %} and {% data variables.enterprise.data_residency_site %} use different provisioning and authentication systems, organization membership is not carried over between platforms. You will need to add users to the organization before you can reattribute activity to them in a migrated repository.
+
+1. If you created a new organization for the migration process, add members to the organization. You can do this manually, but many enterprises manage organization membership from their identity provider (IdP) by syncing enterprise teams with IdP groups.
+1. Add organization members to the migrated repositories.
+
+## Reattribute activity to users
+
+{% data reusables.enterprise-migration-tool.about-mannequins %} For more information, see [AUTOTITLE](/migrations/overview/mannequins-and-user-activity).
+
+Once user accounts have been added to the organization on {% data variables.enterprise.data_residency_site %}, you can invite users to reclaim a mannequin's activity. You can do this in the browser or, with the {% data variables.product.prodname_gei_cli %} tool, reclaim mannequins in bulk without the invite process.
+
+### Reclaiming mannequins in the browser
+
+{% data reusables.elm.reclaim-mannequins-in-browser %}
+
+### Reclaiming mannequins in bulk
+
+You can install the {% data variables.product.prodname_gei_cli %} to reclaim mannequins in bulk. See [AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer#reclaiming-mannequins-with-the-gei-extension).
+
+## Reattribute Git activity
+
+{% data reusables.elm.git-activity %}
+
+To reattribute Git activity on {% data variables.enterprise.data_residency_site %}, ensure the user's primary email address in your identity provider (IdP) matches the email address used for their commits. With {% data variables.product.prodname_emus %}, users cannot add email addresses to their user account on {% data variables.product.github %}, so users will not be able to reattribute their Git commits independently.
+
+## Recreate organization settings
+
+If you created a new organization for the migration process, restore settings such as policies, organization teams, and projects.

content/migrations/elm/elm-cli-reference.md

@@ -0,0 +1,67 @@
+---
+title: Enterprise Live Migrations CLI reference
+shortTitle: ELM CLI reference
+intro: 'Detailed usage information for the {% data variables.product.prodname_elm_short %} CLI tool.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+contentType: reference
+---
+
+{% data reusables.elm.preview-note %}
+
+## `elm migration` commands
+
+| Command | Description |
+|---|---|
+| `elm migration create` | Creates a new migration for a single source repository |
+| `elm migration start --migration-id MIGRATION-ID` | Starts a migration |
+| `elm migration status --migration-id MIGRATION-ID` | Shows the status, progress, cutover readiness, and timing of a migration |
+| `elm migration list` | Lists all migrations and their statuses |
+| `elm migration cancel --migration-id MIGRATION-ID` | Cancels a migration in progress |
+| `elm migration cutover-to-destination --migration-id MIGRATION-ID` | Initiates the final cutover, locking the source repository and completing the migration |
+
+Some of these commands can take additional options. See the later sections in this article.
+
+## `elm migration create` options
+
+Create a new migration to prepare for repository export and import.
+
+| Flag | Required | Default | Description |
+|---|---|---|---|
+| `--source-org` | Yes | N/A | Slug of the source organization on {% data variables.product.prodname_ghe_server %} |
+| `--source-repo` | Yes | N/A | Name of the source repository |
+| `--target-org` | Yes | N/A | Slug of the destination organization on {% data variables.enterprise.data_residency_site %} |
+| `--target-repo` | Yes | N/A | Name of the destination repository |
+| `--target-api` | Yes | N/A | {% data reusables.elm.ghe-url-description %} |
+| `--pat-name` | Yes | N/A | This must be set to a static string: `system-pat` |
+| `--target-visibility` | No | `internal` | Visibility of the destination repository. Must be `private` or `internal`. Public repositories are not supported. |
+| `--start` | No | `false` | Automatically starts the migration after creating it |
+
+## `elm migration list` options
+
+| Flag | Required | Default | Description |
+|---|---|---|---|
+| `--status` | No | N/A | Filters results by migration status. Valid values: `created`, `queued`, `in_progress`, `paused`, `completed`, `failed`, `terminated`. |
+| `--page-size` | No | N/A | Number of results per page |
+| `--after` | No | N/A | Cursor for pagination, from a previous response |
+
+## `elm migration cutover-to-destination` options
+
+| Flag | Required | Default | Description |
+|---|---|---|---|
+| `--migration-id` | Yes | N/A | The ID of a migration that is ready for cutover. |
+| `--force` | No | `false` | By default, the command checks whether the migration target reports readiness before proceeding. Use `--force` to bypass this check when you are certain the migration state is correct. |
+
+## Global flags and variables
+
+The following properties can be provided either as environment variables or as flags on any command, with command flags taking priority. You should set these values _after_ applying the `ghe-config` configuration.
+
+| Variable | Flag | Required | Description |
+|----------|------|----------|-------------|
+| API_URL | `--api-url` | Yes | Must be set to `{% data reusables.elm.localhost-value %}`. |
+| MIGRATION_MANAGER_HMAC_KEY | `--migration-manager-hmac-key` | Yes | Must be set to `{% data reusables.elm.hmac-key-value %}`. |
+| MIGRATION_TARGET_URL | `--migration-target-url` | Yes | {% data reusables.elm.ghe-url-description %} |
+| MIGRATION_TARGET_TOKEN | `--migration-target-token` | Yes | {% data reusables.elm.ghe-pat-description %} |
+| DEBUG_HTTP | `--debug-http` | No | Set to `true` to print the HTTP method, URL, headers, and error response body for each request, for debugging purposes |

content/migrations/elm/index.md

@@ -0,0 +1,17 @@
+---
+title: Live migrations from GitHub Enterprise Server to GHE.com
+shortTitle: Live migrations (GHES to GHE.com)
+intro: 'Use the Enterprise Live Migrations tool to migrate repositories with minimal downtime for developers.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+children:
+  - /about-live-migrations
+  - /prepare-for-your-migration
+  - /migrate-your-repository
+  - /complete-your-migration
+  - /troubleshooting
+  - /migrated-data-reference
+  - /elm-cli-reference
+---