Help Center/ CodeArts Repo/ User Guide/ Migrating Code and Syncing a Repository/ Migrating a Third-Party Git Repository to CodeArts Repo/ Migrating a Git Repository Using a URL
Updated on 2026-05-14 GMT+08:00
Migrating a Git Repository Using a URL
Constraints
- You need to create a new project or select an existing one.
- You have the permission to create a repository. If not, refer to Configuring Repo-Level Permissions.
- The repository domain must be connected to the service node.
- Currently, Git supports the following external import sources: bitbucket.org, code.aliyun.com, coding.net, git.qcloud.com, gitee.com, github.com, gitlab.com, visualstudio.com and xiaolvyun.baidu.com.
- After a code repo is created, only the creator can access the repo. Other project members need to be manually added to the repository and assigned with corresponding permissions. Therefore, you need to manually add members to the repository and configure access permissions for the new members by referring to Configuring Repo-Level Permissions.
Steps
- Go to the CodeArts Repo homepage, click New Repository, and select an existing project from the Project drop-down list box or create a project.
- Set the repository type to Import, and import from Git URL. For details about how to set parameters, see Table 1.
Table 1 Parameters for obtaining authorization Parameter
Description
Source Repository URL
Specifies the repo path to be imported. The source repository path must start with http:// or https:// and end with .git.
Verification to Access Source Repo
There are two cases:
- If the imported source repository is open to all visitors, select Not needed.
- If the imported source repository is private, select Needed. Currently, the repositories can be verified through service endpoint and username and password. For details about how to set the parameters, see Verifying the Import Permission.
- Click Next. On the Basic Information page, set parameters by referring to the parameter table.
- Set the parameters for syncing a repo by referring to table 1. After the parameters are set, the Code page for creating the repo is displayed.
Helpful Links
- If the repository file is too large or the network quality is poor, it may take more than 30 minutes to import the file. If the import times out, clone and push the repository to the client. For details, see When a Git-based Remote Repository Is Imported to CodeArts Repo, an Error Message "Accessing the remote repository timed out. Check the network." Is Displayed..
- On the repository list page, if the new repository name is in gray with a red exclamation mark next to it, the repository fails to be imported. The possible cause is that the username, password, or access token is incorrect. You can delete the repository and import the external repository again according to Migrating a Git Repository Using a URL.
Parent topic: Migrating a Third-Party Git Repository to CodeArts Repo
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot