Repository migrate
AtomGit provides a repository migration function, allowing users to import GitHub and Gitee repository data through personal access keys (PAT). Currently, it supports the import of basic information and git warehouses.
Prepare personal access key
To use AtomGit's repository migration function, you need to first prepare the Personal Access Token corresponding to the repository hosting platform. Through this key, AtomGit can obtain repository information from platforms such as GitHub and Gitee.
- Generate a personal access key for GitHub:
- Log in to GitHub and open [Settings]
- Select [Developer settings] in the left navigation
- Select [Personal access tokens]
- Click the [Generate new token] button
- Fill in the Token description, select the repo permissions, and click the [Generate token] button
- Copy the generated Token and keep it properly
- Apply for Gitee's private token:
- Log in to Gitee and open [Personal Center]
- Select [Private Token] in the left navigation
- Fill in the token name and validity period, select the repo permissions, and click the [Create Token] button
- Copy the generated token and keep it properly
It is recommended that the permissions of the personal access key be set to the read-only permissions of the repository, and must include the repo permissions, otherwise the repository information will not be obtained.
Migrate repository
- Open AtomGit, click the "+" sign in the upper right corner, and select [Import repository]
- Choose which platform to migrate the repository from. GitHub and Gitee are currently supported.
- Select the namespace to which the repository will belong after migration, including the user's own and the organization's namespace.
- Enter the personal access key for the corresponding platform and click [OK]
The selected namespace is only the default ownership, and the ownership of each repository can be modified in the import interface.
Import repository
After completing the above steps, you will enter the repository list page to be imported, which will display:
-Token information used and user name of the corresponding platform
- List of all repositories, including private, organization-wide repositories and repositories participating as collaborators
- repository import status: not imported, importing, import successful
- The repository address of the original platform and the imported AtomGit address
- Supported operations:
- Change Token
- Batch Import
- single import
- Search repository
- Re-obtain the repository list
You can import single or multiple repositories on this page, modify the ownership of each repository, view the imported repositories, etc.
Common problems
- What should I do if I want to change the ownership of the repository?
- Unimported repository:
- Find the repository
- Click Modify Attribution
- Select the new ownership and save
- Click the [Import] button
- Imported repository:
- Enter the repository settings and delete the repository
- Return to the repository list to be imported and modify the ownership
- Select the owning namespace
- Click the [Import] button
- I forgot the token I used last time. Do I need to regenerate it?
No, AtomGit will use the last Token by default. As long as the Token has not been deleted and is still valid, it can continue to be used.
- Can the Token be deleted in GitHub/Gitee after importing?
Removal is possible but not recommended. In addition to importing the repository, AtomGit will use this token to synchronize the imported repository from the original platform every day. If the Token is deleted, the imported repository will not be updated synchronously. If synchronous updates are not required, the Token can be deleted.