Deprecation announcement for non-Git repository imports in GitHub Importer (SVN, Mercurial, TFVC) (github#36378)

Co-authored-by: Tim Rogers <[email protected]>
Co-authored-by: Siara <[email protected]>

Author: 3 people

content/get-started/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md

@@ -68,4 +68,4 @@ SVN is configured to assume that the history of a project never changes. Git all
 ## Further reading
 
 - ["Branching and Merging" from the _Git SCM_ book](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
-- "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/source-code-migration-tools)"
+- "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-subversion-repository)"

content/migrations/importing-source-code/using-github-importer/about-github-importer.md

@@ -19,6 +19,8 @@ During an import, depending on the version control system you're importing from,
 
 ## Supported functionality by version control system
 
+{% data reusables.migrations.github-importer-non-git-deprecation %}
+
 {% rowheaders %}
 
 | Import action | Subversion | Mercurial | TFVC | Git |
@@ -33,4 +35,3 @@ During an import, depending on the version control system you're importing from,
 ## Further reading
 
 - "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line)"
-- "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/source-code-migration-tools)"

content/migrations/importing-source-code/using-github-importer/importing-a-repository-with-github-importer.md

@@ -12,16 +12,19 @@ versions:
   ghec: '*'
 shortTitle: Import a repository
 ---
-{% tip %}
 
-**Tip:** GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend [importing using the command line](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line) for Git repositories or an external [source code migration tool](/migrations/importing-source-code/using-the-command-line-to-import-source-code/source-code-migration-tools) for projects imported from other version control systems.
+## About repository imports with GitHub Importer
 
-{% endtip %}
+GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend [importing using the command line](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line) for Git repositories or an external [source code migration tool](/migrations/importing-source-code/using-the-command-line-to-import-source-code) for projects imported from other version control systems.
+
+{% data reusables.migrations.github-importer-non-git-deprecation %}
 
 If you'd like to match the commits in your repository to the authors' GitHub personal accounts during the import, make sure every contributor to your repository has a GitHub account before you begin the import.
 
 {% data reusables.repositories.repo-size-limit %}
 
+## Importing a repository with GitHub Importer
+
 1. In the upper-right corner of any page, click {% octicon "plus" aria-label="Create new..." %}, and then click **Import repository**.
 
    ![Screenshot of the top-right corner of any page on {% data variables.product.prodname_dotcom %}. A plus icon is highlighted with an orange outline.](/assets/images/help/importer/import-repository.png)

content/migrations/importing-source-code/using-the-command-line-to-import-source-code/about-source-code-imports-using-the-command-line.md

@@ -0,0 +1,40 @@
+---
+title: About source code imports using the command line
+intro: 'You can use command line tools to import source code and its revision history to {% data variables.product.product_name %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: About source code imports
+---
+
+
+{% ifversion fpt or ghec %}
+
+If you want to import a Git repository that is stored on a code hosting service that is publicly available on the internet, we recommend using GitHub Importer. For more information, see "[AUTOTITLE](/migrations/importing-source-code/using-github-importer)."
+
+If your source code is not tracked by Git or is not publicly available, you can use the command line instead.
+
+{% else %}
+
+You can use the command line to import source code and, if the code has been tracked using a version control system like Git, the code's revision history.
+
+{% endif %}
+
+- To import a Git repository that is stored on a code hosting service{% ifversion fpt or ghec %} that is not accessible from the public internet{% endif %}, see "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line)."
+- To import code that is only stored locally, and is either tracked by Git or not tracked by any version control system, see "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/adding-locally-hosted-code-to-github)."
+- To import code that is tracked by any version control system other than Git, first convert the repository to Git, then push the Git repository to {% data variables.product.product_name %}.
+{% ifversion fpt or ghec or ghae %}
+   - "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-subversion-repository)"
+   - "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-mercurial-repository)"
+   - "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository)"
+{% else %}
+   - End users can use third-party conversion tools.
+      - "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-subversion-repository)"
+      - "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-mercurial-repository)"
+      - "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository)"
+   - Site administrators can use the administrative shell. For more information, see "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-from-other-version-control-systems-with-the-administrative-shell)."
+{% endif %}
+
+All of these tools import source code and revision history, only. If you also want to import your settings and your collaboration history, such as issues and pull requests, you'll need to use more advanced tools. To determine the best tool to use for your migration, see "[AUTOTITLE](/migrations/overview/planning-your-migration-to-github)."