updating content files
This commit is contained in:
Grace Park
@@ -20,7 +20,7 @@ During an import, depending on the version control system you're importing from,
|
||||
| Move large files to [Git Large File Storage](/articles/about-git-large-file-storage) | **X** | **X** | **X** | |
|
||||
| Remove large files from your repository | **X** | **X** | **X** | |
|
||||
|
||||
### Further reading
|
||||
## Further reading
|
||||
|
||||
- "[Importing a repository with GitHub Importer](/articles/importing-a-repository-with-github-importer)"
|
||||
- "[Updating commit author attribution with GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)"
|
||||
|
||||
@@ -131,6 +131,6 @@ versions:
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
### Further reading
|
||||
## Further reading
|
||||
|
||||
- "[Adding a file to a repository using the command line](/articles/adding-a-file-to-a-repository-using-the-command-line)"
|
||||
|
||||
@@ -39,6 +39,6 @@ If you'd like to match the commits in your repository to the authors' GitHub use
|
||||
|
||||
You'll receive an email when the repository has been completely imported.
|
||||
|
||||
### Further reading
|
||||
## Further reading
|
||||
|
||||
- "[Updating commit author attribution with GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)"
|
||||
|
||||
@@ -16,7 +16,7 @@ We recommend using [GitHub Importer](/articles/about-github-importer) to import
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Importing from Subversion
|
||||
## Importing from Subversion
|
||||
|
||||
In a typical Subversion environment, multiple projects are stored in a single root repository. On GitHub, each of these projects will usually map to a separate Git repository for a user account or organization. We suggest importing each part of your Subversion repository to a separate GitHub repository if:
|
||||
|
||||
@@ -28,11 +28,11 @@ We recommend these tools for converting Subversion repositories to Git:
|
||||
- [`git-svn`](https://git-scm.com/docs/git-svn)
|
||||
- [svn2git](https://github.com/nirvdrum/svn2git)
|
||||
|
||||
### Importing from Mercurial
|
||||
## Importing from Mercurial
|
||||
|
||||
We recommend [hg-fast-export](https://github.com/frej/fast-export) for converting Mercurial repositories to Git.
|
||||
|
||||
### Importing from TFVC
|
||||
## Importing from TFVC
|
||||
|
||||
We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
|
||||
|
||||
@@ -44,7 +44,7 @@ We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes be
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
### Further reading
|
||||
## Further reading
|
||||
|
||||
- "[About GitHub Importer](/articles/about-github-importer)"
|
||||
- "[Importing a repository with GitHub Importer](/articles/importing-a-repository-with-github-importer)"
|
||||
|
||||
@@ -9,7 +9,7 @@ versions:
|
||||
---
|
||||
GitHub Importer looks for GitHub 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 GitHub username.
|
||||
|
||||
### Updating commit authors
|
||||
## Updating commit authors
|
||||
|
||||
1. After you've imported your repository, on the import status page, click **Match authors**.
|
||||
|
||||
@@ -17,23 +17,23 @@ GitHub Importer looks for GitHub users whose email addresses match the authors o
|
||||
|
||||
3. Type the email address or GitHub username of the author, then press **Enter**.
|
||||
|
||||
### Attributing commits to a GitHub user with a public email address
|
||||
## Attributing commits to a GitHub user with a public email address
|
||||
|
||||
If the author of a commit in your imported repository has a GitHub account associated with the email address they used to author the commits, and they haven't [set their commit email address as private](/articles/setting-your-commit-email-address), GitHub 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 GitHub account.
|
||||
|
||||
### Attributing commits to a GitHub user without a public email address
|
||||
## Attributing commits to a GitHub 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 GitHub profile, nor [set their commit email address as private](/articles/setting-your-commit-email-address), GitHub Importer may not be able to match the email address associated with the commit with their GitHub account.
|
||||
|
||||
The commit author can resolve this by setting their email address as private. Their commits will then be attributed to `<username>@users.noreply.github.com`, and the imported commits will be associated with their GitHub account.
|
||||
|
||||
### Attributing commits using an email address
|
||||
## Attributing commits using an email address
|
||||
|
||||
If the author's email address is not associated with their GitHub account, they can [add the address to their account](/articles/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 GitHub account, GitHub Importer will attribute their commits to the email address associated with the commits.
|
||||
|
||||
### Further reading
|
||||
## Further reading
|
||||
|
||||
- "[About GitHub Importer](/articles/about-github-importer)"
|
||||
- "[Importing a repository with GitHub Importer](/articles/importing-a-repository-with-github-importer)"
|
||||
|
||||
Reference in New Issue
Block a user