- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Process of CodeArts Repo
- Purchasing CodeArts
- Environment and Personal Settings
- Accessing CodeArts Repo Homepage
- Configuring Project-Level Settings for CodeArts Repo
- Managing Member Permissions
- Creating a Repository
- Migrating Code and Syncing a Repository
- Configuring Repository Settings
- Hierarchical Repository Management
- Viewing Repository Information
- Cloning or Downloading a Repository to a Local PC
- Uploading Code Files to CodeArts Repo
- Collaborating on a Workflow
- Committing Code to CodeArts Repo and Managing a Merge Request
- Managing Code Files
- Security Management
-
Best Practices
- CodeArts Repo Best Practices
- Managing Repository Members and Permissions in an Enterprise
- Migrating GitLab Intranet Repositories to CodeArts Repo in Batches
- Importing Local Repositories to CodeArts Repo in Batches
- CodeArts Repo Security Configuration Overview
- Configuring HTTPS Password
- Best Practices for Configuring Protected Branch Rules
-
FAQs
- Authentication
- Member Permissions
-
Uploading and Downloading Code
- "Error: Deny by project hooks setting 'default': message of commit" Is Reported When Code Repository Is Pushed from the Local Host to CodeArts Repo
- Pushing Binary Files to CodeArts Repo Failed
- Error "'origin' does not appear to be a git repository..." Is Reported When the Git Push Command Is Executed
- Error "The requested URL returned error: 401" Is Reported When HTTPS Is Used to Clone Code in CentOS
- Error "Merge branch 'master' of https://test.com Please Enter a commit" Is Reported When Pulling Code Using the Git Pull Command
- Message "fatal: refusing to merge unrelated histories" Is Displayed
- How Do I Prevent Files Containing Secrets from Being Pushed to CodeArts Repo?
- Migrating Repositories
- Merge Request
- Fork Sync
- Repository Capacity
- FAQs
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
- SSH Key
-
Repository
- Obtaining Files in a Branch Directory
- Obtaining Repository Statistics
- Obtaining Image Files of a Specific Branch in a Repository
- Modifying the Status of a Repository Referenced by a Pipeline
- Checking Whether a User Has the Repository Administrator Permission
- Setting a Repository to Public or Private
- Obtaining the Content of a Specified File in a Specified Branch of a Repository
- Obtaining a Public Template List
- Creating a Repository
- Obtaining a Repository Short ID to Generate the Details Page URL
- Querying a Commit of a Branch by Repository or Repository Group Name
- Querying Branches of a Specified Repository
- Querying a Commit of a Repository Branch by the Repository ID
- Adding a Deploy Key
- Deleting a Deploy Key
- Obtaining the Last Commit Statistics of a Repository
- Repository Statistics
- Deleting a Repository
- Viewing a Repository Creation Status
- Querying the Tag List of a Repository
- Adding a Tag
- Querying Details About a Repository
- Obtaining the number of committed code lines
- Downloading a Repository
- Creating a Protected Branch
- Deleting a Protected Branch
- Deleting Protected Branches in Batches
- Creating a Protected Tag
- Deleting a Protected Tag
- Obtaining a Repository Branch List
- Obtaining the MR List of a Repository
- Obtaining MR Details of a Repository
- Obtaining the Repository IP Address Whitelist
- Adding the Repository IP Address Whitelist
- Modifying the Repository IP Address Whitelist
- Deleting the Repository IP Address Whitelist
- Obtaining the Changes of an MR
- Associating a Repository with a Member Group
- Locking a Repository Based on the Repository Short ID
- Unlocking a Repository Based on the Repository Short ID
- Approving an MR
- Obtaining Associated Work Item Information
- Obtaining Reviewer Information Based on the Repo Short ID and Merge Request Short ID
- Obtaining the List of Changed Files
- Tenant
- Group
- Project (V2)
- RepoMember
- Commit
- File
- User
- Webhook
- Project
- Repository Management (V2)
- Review
- Application Examples
- Appendix
- Videos
- General Reference
Show all
Copied.
Process of CodeArts Repo
The following figure shows how to use CodeArts Repo.

Process |
Description |
---|---|
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. |
Repository administrators can create repositories. Repository administrators can also import repositories. Developers can develop code based on the imported repositories.
|
|
|
|
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.
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. |
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. 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.
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. |
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot