3.5 KiB
3.5 KiB
title, intro, redirect_from, versions
| title | intro | redirect_from | versions | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| About GitHub Importer | If your source code is stored on another Git-based hosting service, you can move the code to {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_importer %}. |
|
|
About {% data variables.product.prodname_importer %}
{% data variables.product.prodname_importer %} is a tool that quickly imports Git repositories from other hosting services to {% data variables.product.prodname_dotcom_the_website %}.
To get started with {% data variables.product.prodname_importer %}, see AUTOTITLE.
Capabilities and limitations of {% data variables.product.prodname_importer %}
- {% data variables.product.prodname_importer %} imports the source code and commit history of a repository. It does not import other associated data from the hosting service, such as issues and pull requests.
- {% data variables.product.prodname_importer %} is only available on {% data variables.product.prodname_dotcom_the_website %}.
- During an import, you can authenticate with your remote repository. The repository must be accessible from the public internet. If the repository is hosted on a private network, {% data variables.product.prodname_importer %} won't be able to access it.
- {% data variables.product.prodname_importer %} does not support repositories that use version control systems other than Git, such as Mercurial, Subversion, or Team Foundation Version Control (TFVC). For more information about alternatives to {% data variables.product.prodname_importer %}, see AUTOTITLE.
- Repositories and individual files on {% data variables.product.prodname_dotcom %} are subject to size limits. For more information, see AUTOTITLE.
- {% data variables.product.prodname_importer %} does not move Git Large File Storage (LFS) objects from the source repository to the target repository. If you use Git LFS, you will need to either convert the Git LFS objects to regular files tracked by Git before running the migration, or move the Git LFS objects to the new repository separately after running the migration.