docs-bot
@@ -1,11 +1,16 @@
|
||||
---
|
||||
title: About GitHub Importer
|
||||
intro: "If your source code is stored on a code hosting service using Git, Subversion, Mercurial, or Team Foundation Version Control (TFVC) and is accessible from the public internet, you can move the code to {% data variables.product.prodname_dotcom %} using {% data variables.product.prodname_importer %}."
|
||||
intro: "If your source code is stored on another Git-based hosting service, you can move the code to {% data variables.product.prodname_dotcom %} using {% data variables.product.prodname_importer %}."
|
||||
redirect_from:
|
||||
- /articles/about-github-importer
|
||||
- /github/importing-your-projects-to-github/about-github-importer
|
||||
- /github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer
|
||||
- /get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer
|
||||
- /articles/updating-commit-author-attribution-with-github-importer
|
||||
- /github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer
|
||||
- /github/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer
|
||||
- /get-started/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer
|
||||
- /migrations/importing-source-code/using-github-importer/updating-commit-author-attribution-with-github-importer
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -13,24 +18,17 @@ versions:
|
||||
|
||||
## About {% data variables.product.prodname_importer %}
|
||||
|
||||
{% data variables.product.prodname_importer %} is a tool that quickly imports source code repositories, including commits and revision history, to {% data variables.product.prodname_dotcom_the_website %} for you.
|
||||
{% data variables.product.prodname_importer %} is a tool that quickly imports Git repositories from other hosting services to {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
During an import, depending on the version control system you're importing from, you can authenticate with your remote repository, update commit author attribution, and either import repositories with large files or, if you don't want to use {% data variables.large_files.product_name_long %}, remove large files.
|
||||
To get started with {% data variables.product.prodname_importer %}, see "[AUTOTITLE](/migrations/importing-source-code/using-github-importer/importing-a-repository-with-github-importer#importing-a-repository-with-github-importer)."
|
||||
|
||||
## Supported functionality by version control system
|
||||
## Capabilities and limitations of {% data variables.product.prodname_importer %}
|
||||
|
||||
{% data reusables.migrations.github-importer-non-git-deprecation %}
|
||||
|
||||
{% rowheaders %}
|
||||
|
||||
| Import action | Subversion | Mercurial | TFVC | Git |
|
||||
|:--------------|:----------:|:---------:|:----------------------:|:---:|
|
||||
| Authenticate with remote repository | {% octicon "check" aria-label="Supported" %}| {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
|
||||
| [Update commit author attribution](/migrations/importing-source-code/using-github-importer/updating-commit-author-attribution-with-github-importer) | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
|
||||
| Move large files to [Git Large File Storage](/repositories/working-with-files/managing-large-files/about-git-large-file-storage) | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
|
||||
| Remove large files from your repository | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
|
||||
|
||||
{% endrowheaders %}
|
||||
- {% 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.
|
||||
- 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](/migrations/importing-source-code/using-the-command-line-to-import-source-code/about-source-code-imports-using-the-command-line)."
|
||||
- Repositories and individual files on {% data variables.product.prodname_dotcom %} are subject to size limits. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github)."
|
||||
- {% 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.
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Importing a repository with GitHub Importer
|
||||
intro: 'If you have a project hosted on another version control system, you can automatically import it to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_importer %} tool.'
|
||||
intro: 'If you have a project hosted on another Git-based hosting service, you can quickly import it to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_importer %} tool.'
|
||||
redirect_from:
|
||||
- /articles/importing-from-other-version-control-systems-to-github
|
||||
- /articles/importing-a-repository-with-github-importer
|
||||
@@ -15,15 +15,9 @@ shortTitle: Import a repository
|
||||
|
||||
## About repository imports with {% data variables.product.prodname_importer %}
|
||||
|
||||
{% data variables.product.prodname_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 variables.product.prodname_importer %} imports the source code and commit history of Git repositories hosted on external hosting services. For more information about the capabilities and limitations of {% data variables.product.prodname_importer %}, see "[AUTOTITLE](/migrations/importing-source-code/using-github-importer/about-github-importer#capabilities-and-limitations-of-github-importer)."
|
||||
|
||||
{% data reusables.migrations.github-importer-non-git-deprecation %}
|
||||
|
||||
If you'd like to match the commits in your repository to the authors' {% data variables.product.prodname_dotcom %} personal accounts during the import, make sure every contributor to your repository has a {% data variables.product.prodname_dotcom %} account before you begin the import.
|
||||
|
||||
{% data reusables.repositories.repo-size-limit %}
|
||||
|
||||
For more information about migration paths to {% data variables.product.prodname_dotcom %} from other products, or between {% data variables.product.prodname_dotcom %} products, see "[AUTOTITLE](/migrations/overview/migration-paths-to-github)."
|
||||
{% data variables.product.product_name %} uses the email address in the commit header to link a commit to a {% data variables.product.prodname_dotcom %} user. To correctly attribute commits in an imported repository, users will need to add the email address associated with their commits to their account on {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)."
|
||||
|
||||
## Importing a repository with {% data variables.product.prodname_importer %}
|
||||
|
||||
@@ -33,14 +27,10 @@ When you import a repository using the {% data variables.product.prodname_import
|
||||
|
||||
|
||||
|
||||
1. Under "Your old repository's clone URL", type the URL of the project you want to import.
|
||||
1. Under "Owner", select the dropdown menu and click your personal account or an organization to own the repository
|
||||
1. Under "Name", type a name for the repository on {% data variables.product.prodname_dotcom %}.
|
||||
1. Under "Privacy", select a visibility for the repository. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)."
|
||||
1. Review the information you entered, then click **Begin import**.
|
||||
1. If your old project requires credentials, type your login information for that project. If SAML SSO or 2FA are enabled for your user account on the old project, enter a {% data variables.product.pat_generic %} with repository read permissions in the "Password" field instead of your password.
|
||||
1. Click **Submit**.
|
||||
1. If there are multiple projects hosted at your old project's clone URL, select the project you'd like to import, then click **Submit**.
|
||||
1. If you're moving from a version control system other than Git and your project contains files larger than 100 MB, select whether to import the large files using [Git Large File Storage](/repositories/working-with-files/managing-large-files), then click **Continue**.
|
||||
1. On the "Import your project to {% data variables.product.prodname_dotcom %}" page, enter the URL for the remote repository hosted on another platform.
|
||||
1. If the source repository is private, enter credentials for authentication. {% data variables.product.prodname_importer %} will use the credentials to perform a `git clone` operation on the source repository.
|
||||
1. Choose an owner and a name for the new repository on {% data variables.product.prodname_dotcom %}.
|
||||
1. Choose the visibility of the new repository. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
|
||||
1. Click **Begin import**.
|
||||
|
||||
You'll receive an email when the repository has been completely imported.
|
||||
You'll be redirected to a "Preparing your new repository" page, where you can track the status of your import. You'll receive an email when the repository has been completely imported.
|
||||
|
||||
@@ -9,6 +9,5 @@ versions:
|
||||
children:
|
||||
- /about-github-importer
|
||||
- /importing-a-repository-with-github-importer
|
||||
- /updating-commit-author-attribution-with-github-importer
|
||||
shortTitle: GitHub Importer
|
||||
---
|
||||
|
||||
@@ -1,41 +0,0 @@
|
||||
---
|
||||
title: Updating commit author attribution with GitHub Importer
|
||||
intro: 'During an import, you can match commits in your repository with the GitHub account of the commit author.'
|
||||
redirect_from:
|
||||
- /articles/updating-commit-author-attribution-with-github-importer
|
||||
- /github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer
|
||||
- /github/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer
|
||||
- /get-started/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Update commit authors
|
||||
---
|
||||
{% data variables.product.prodname_importer %} looks for {% data variables.product.prodname_dotcom %} users whose email addresses match the authors of the commits in the repository you're importing. You can then connect a commit to its author using their email address or the author's {% data variables.product.prodname_dotcom %} username.
|
||||
|
||||
## Updating commit authors
|
||||
|
||||
1. After you've imported your repository, on the import status page, click **Match authors**.
|
||||
1. Next to the author whose information you'd like to update, click **Connect**.
|
||||
1. Type the email address or {% data variables.product.prodname_dotcom %} username of the author, then press **Enter**.
|
||||
|
||||
## Attributing commits to a {% data variables.product.prodname_dotcom %} user with a public email address
|
||||
|
||||
If the author of a commit in your imported repository has a {% data variables.product.prodname_dotcom %} account associated with the email address they used to author the commits, and they haven't [set their commit email address as private](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address), {% data variables.product.prodname_importer %} will match the email address associated with the commit to the public email address associated with their GitHub account, and attribute the commit to their {% data variables.product.prodname_dotcom %} account.
|
||||
|
||||
## Attributing commits to a {% data variables.product.prodname_dotcom %} user without a public email address
|
||||
|
||||
If the author of a commit in your imported repository has neither set a public email address on their {% data variables.product.prodname_dotcom %} profile, nor [set their commit email address as private](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address), {% data variables.product.prodname_importer %} may not be able to match the email address associated with the commit with their {% data variables.product.prodname_dotcom %} account.
|
||||
|
||||
The commit author can resolve this by setting their email address as private. Their commits will then be attributed to a no-reply email, and the imported commits will be associated with their GitHub account. For more information about the exact form the no-reply email address can take, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)."
|
||||
|
||||
## Attributing commits using an email address
|
||||
|
||||
If the author's email address is not associated with their {% data variables.product.prodname_dotcom %} account, they can [add the address to their account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account) after the import, and the commits will be correctly attributed.
|
||||
|
||||
If the author does not have a {% data variables.product.prodname_dotcom %} account, {% data variables.product.prodname_importer %} will attribute their commits to the email address associated with the commits.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)"
|
||||
- "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)"
|
||||
@@ -15,12 +15,6 @@ To learn more about "source and history" and other types of migrations, see "[AU
|
||||
|
||||
The term "source repository" refers to the repository you're importing, and "imported repository" refers to the new repository you're creating.
|
||||
|
||||
### About the deprecation of the Source imports REST API
|
||||
|
||||
The REST API endpoints to manage source imports allowed the programmatic import of a repositories that are accessible over the internet to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[AUTOTITLE](/rest/migrations/source-imports)."
|
||||
|
||||
On April 12, 2024, {% data variables.product.company_short %} will deprecate all of the endpoints listed within "[AUTOTITLE](/rest/migrations/source-imports)." If you currently use these operations, you'll need to make changes to your code or your application will stop working on April 12, 2024.
|
||||
|
||||
## Using forks
|
||||
|
||||
If the source repository is on {% data variables.product.prodname_dotcom_the_website %}, you may be able to use a fork instead of importing the repository. {% data reusables.repositories.about-forks %} For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
|
||||
|
||||
@@ -17,7 +17,7 @@ topics:
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you have a project hosted on another version control system, you can automatically import your project to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_importer %} tool. For more information, see "[AUTOTITLE](/migrations/importing-source-code/using-github-importer/about-github-importer)."
|
||||
**Note:** If you have a project hosted on another Git-based hosting service, you can automatically import your project to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_importer %} tool. For more information, see "[AUTOTITLE](/migrations/importing-source-code/using-github-importer/about-github-importer)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -3,8 +3,7 @@ title: REST API endpoints for source imports
|
||||
shortTitle: Source endpoints
|
||||
allowTitleToDifferFromFilename: true
|
||||
intro: >-
|
||||
Use the REST API to start an import from a Git, Subversion, Mercurial, or Team
|
||||
Foundation Version Control source repository.
|
||||
Use the REST API to start an import from a Git source repository.
|
||||
versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -17,7 +16,7 @@ autogenerated: rest
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Due to very low levels of usage and available alternatives, the Source Imports API is deprecated and will no longer be available from 00:00 UTC on April 12, 2024. For more details and alternatives, see the [changelog](https://gh.io/source-imports-api-deprecation).
|
||||
**Warning**: Due to very low levels of usage and available alternatives, the Source Imports API has been deprecated and is no longer available as of April 12, 2024. For more details and alternatives, see the [changelog](https://gh.io/source-imports-api-deprecation).
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
|
||||
@@ -1,5 +0,0 @@
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Support for importing Mercurial, Subversion and Team Foundation Version Control (TFVC) repositories using {% data variables.product.prodname_importer %} will end on April 12, 2024. For more information, see the [changelog](https://github.blog/changelog/2023-04-17-deprecation-importing-non-git-repositories-with-github-importer/).
|
||||
|
||||
{% endwarning %}
|
||||
@@ -3,7 +3,6 @@ user_migrations_intro: >-
|
||||
organization_migrations_intro: >-
|
||||
You can use these endpoints to export one or more repositories so you can move them to a{% ifversion ghes %}nother{% endif %} {% data variables.product.prodname_ghe_server %} instance. For more information, see "[AUTOTITLE](/migrations/using-ghe-migrator/exporting-migration-data-from-githubcom)."
|
||||
source_imports_intro: >-
|
||||
You can use these endpoints to start an import from a Git, Subversion,
|
||||
Mercurial, or Team Foundation Version Control source repository. This is the same
|
||||
You can use these endpoints to start an import from a Git repository hosted with another service. This is the same
|
||||
functionality as the {% data variables.product.prodname_dotcom %}
|
||||
Importer. For more information, see "[AUTOTITLE](/migrations/importing-source-code/using-github-importer/importing-a-repository-with-github-importer)."
|
||||
|
||||
Reference in New Issue
Block a user