CodeArts Repo Best Practices

**Table 1** Common best practices
Practice	Description
Migrating GitLab Intranet Repositories to CodeArts Repo in Batches	Currently, CodeArts Repo only allows for repository migrations between public networks. There is no quick solution for migrating repositories from a platform built on the customer's intranet to CodeArts Repo. Therefore, we provide a script for migrating repositories from an intranet platform to CodeArts Repo in batches.
Importing External Repositories to CodeArts Repo in Batches	Currently, CodeArts Repo only allows for repository migrations between public networks. There is no quick solution for migrating repositories from a platform built on the customer's intranet to CodeArts Repo. Therefore, we provide a script for migrating repositories from an intranet platform to CodeArts Repo in batches.
CodeArts Repo Security Configuration Overview	CodeArts Repo provides access tokens, deploy keys, and protected branches to safeguard your code assets.
Managing Repository Members and Permissions in an Enterprise	CodeArts Repo supports project-level, repository group-level, and repository-level permissions. This section uses project development as an example to describe how to configure CodeArts Repo permissions for different roles in an enterprise.
Configuring HTTPS Password	When you push code to or pull code from CodeArts Repo, the repository verifies your identity and permissions. HTTPS password is an identity authentication mode for remote access to CodeArts Repo. You only need to set this once.
Configuring Project-level Protected Branch Rules	Set up protected branch rules during collaborative coding to enhance code quality, safeguard branches, and boost teamwork for reliable, secure software delivery.