Remove reference to broken ghe-migrator target_url command (github#…

…34968)
bulutibo · Feb 22, 2023 · 5507dac · 5507dac
1 parent be9d598
commit 5507dac
Showing 1 changed file with 0 additions and 6 deletions.
diff --git a/...ta-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/...ta-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
@@ -75,12 +75,6 @@ shortTitle: Export from your enterprise
   ```
   Each time you add a new repository with an existing Migration GUID it will update the existing export. If you run `ghe-migrator add` again without a Migration GUID it will start a new export and generate a new Migration GUID. **Do not re-use the Migration GUID generated during an export when you start preparing your migration for import**.
 
-3. If you locked the source repository, you can use the `ghe-migrator target_url` command to set a custom lock message on the repository page that links to the repository's new location. Pass the source repository URL, the target repository URL, and the Migration GUID from Step 5:
-
-  ```shell
-  $ ghe-migrator target_url https://HOSTNAME/USERNAME/REPO-NAME https://TARGET-HOSTNAME/TARGET-USER-NAME/TARGET-REPO-NAME -g MIGRATION-GUID
-  ```
-
 6. To add more repositories to the same export, use the `ghe-migrator add` command with the `-g` flag. You'll pass in the new repository URL and the Migration GUID from Step 5:
   ```shell
   $ ghe-migrator add https://HOSTNAME/USERNAME/OTHER-REPO-NAME -g MIGRATION-GUID --lock