Process of CodeArts Repo

Create and Configure a CodeArts Project

All CodeArts Repo operations must be performed in a project. You need to create a CodeArts project. By doing this, you can create a CodeArts project, add project members, and manage members' permissions to use other CodeArts services.

Create a Repository in a Project

Repository administrators can create repositories.

• Creating a Custom Repository
• Creating a Repository Using a Template

Repository administrators can also import repositories. Developers can develop code based on the imported repositories.

• Migrating a Git Repository Using a URL
• Migrating a GitHub Repository
• Migrating a GitLab Repository
• Migrating a Self-Built GitLab Repository
• Migrating a GitHub Repository
• Migrating a Coding Repository
• Migrating a Codeup Repository
• Migrating a Bitbucket Repository
• Migrating a Gerrit Repository
• Migrating an SVN Repository

Configure Member Permissions

• Repository administrators can configure CodeArts Repo permissions for project members of the repository. For details, see Configuring Project-Level Permissions.
• Repository administrators can configure permissions for repository members. For details, see Configuring Repo-Level Permissions.
• Project members can be synced to the repository or repository group. For details, see Syncing Project Members to CodeArts Repo.

Configure repository rules

CodeArts Repo allows repository administrators to set rules for repositories to ensure code security. Repository rules can be configured at the project level and repository level.

• Project-level repository rules are as follows:

  Configuring Project-Level Repository Settings, Configuring Protected Branch Rules, Configuring Protected Tags Rules, Configuring Code Commit Rules, Configuring Project-Level Merge Request Rules, E2E Settings, Configuring Webhook Settings, Configuring a Deploy Key for a Repository, Adding Watermarks to a Repository, and Syncing Project Members to CodeArts Repo.

• The repository group rules are as follows:

Repository Group Information, Configuring Repository Settings in a Repository Group, and Risky Operations.

Configure the Git environment

Before cloning a repository to the local host for code development, developers need to install and configure the Git client and configure at least one type of key.

• Installing and Configuring Git
• Configuring an SSH Key
• Configuring an HTTPS Password
• Configuring an Access Token
• Configuring a GPG Public Key

Clone a repository to a local PC

Before code development, developers need to clone the repository to the local host using an SSH key or HTTPS.

• Using the SSH Key to Clone a Repo to a Local PC
• Using HTTPS to Clone a Repo to a Local Computer

If repository members do not develop code, they can download the repository to the local host for viewing. For details, see Using a Browser to Download Code Package to a Local PC.

Coding

You can clone a repository to the local host for code development. You can also develop code online. For details, see Editing and Creating a Merge Request.

Code commit

After developing and checking code on the local host, you can upload the code file to CodeArts Repo.

• You can upload code to Repo through Git Bash. For details, see Creating a Branch and Developing Code in Git Bash.
• You can upload code to Repo through Eclipse. For details, see Committing Code in Eclipse and Creating a Merge Request.
• You can also use the git-crypt command on the Git client to transfer sensitive data to CodeArts Repo to keep your code secure. For details, see Using git-crypt to Transmit Sensitive Data on the Git Client.

Code conflicts may occur when you upload code. For details, see Resolving Code Conflicts in an MR. After the code file is uploaded, you can view the commit history of the code. For details, see Viewing Commit History.

Code check

If the repository administrator selects Automatically create Check task (free of charge) when creating a repository, a CodeArts Check task will be automatically triggered for code specifications check after the code is committed.

Code review

After the code passes the check, the code reviewer can organize code review. They can provide review comments based on the configuration of the repository administrator. For details, see 1.

Approve and merge code in to the master branch

If the repository administrator sets the review comment gate, you need to pass the review comment gate by referring to Passing of the Gate. Then, the committer can merge the MR.