Viewing Repository Details

Updated on 2024-12-12 GMT+08:00

View PDF

In the repository list, click a repository name to go to the repository details page. CodeArts Repo provides abundant operations.

**Table 1** Description
Page	Function Description
Repository Homepage	Displays the repository capacity, number of commits, branches, tags, and members, LFS usage, creation time, creator, visible scope, repository status, README file, language, and percentage of each language.
Code	File list: You can create files, directories, and submodules, upload files, modify files and blame, and view commit history. Submit: You can view commit records and repository network diagrams. Branch: Branches can be managed on the console. Tag: Tags can be managed on the console. Comparison: You can view code changes between branches or between tag versions by comparison.
Merge Requests	Merge requests of branches can be managed on the console.
Reviews	You can view the review records of MRs and commits.
Associated Work Items	List of associated work items. You can associate CodeArts Req work items with the repository code to improve efficiency.
Repository Statistics	Visualized charts of repository commits, such as code contribution.
Activities	You can view the dynamic information about the repository.
Members	Member management is supported. The details are as follows: All, Groups, Pending, and Add Member are located on the Members tab page of repository details. Username, User Source, Project Member Role, and Repository Member Role of all members in the repository are displayed in All. Member Group Name, Number of members, Description, and Operation of all member groups in the repository are displayed in Groups. Pending displays the members to be reviewed in the repository, including their Username, Status, Project Member Role, Repository Group Role, and Operation. A user with permission to add members can set a member to be reviewed as either Agree or Reject. You can add members or member groups to a repository on the Add Member page.
Settings	Entry for setting the repository. All repository members can view this page. For details about whether a repository member has repository setting permissions, refer to the Permissions page.

In addition, the repository details page provides quick entries to the following functions:

Create Build Task: Create a build task.
Follow: Click to follow the repository. The followed repositories are pinned on top.
Fork: displays the number of forks of the repository. Click this button, the Fork Repository page is displayed.
Clone/Download: You can obtain the SSH address and HTTPS address of a repository or directly download the code package.

NOTE:

The following figures show the adaptation function of CodeArts Repo. When the length of the repository page is greater than the window length, the repository tab page is moved to the top after you scroll down. The position in the red box in the following figure is collapsed so you can view repository information easily. After you scroll up, the page layout is restored.
Rules for displaying the code check status:
- If you have the code check permission, the code check status is displayed next to the repository name.
- If you do not have the code check permission, no code check status is displayed next to the repository name.
Rules for displaying the build status:
- If you do not have the build permission,
  only the Create Build Task button is displayed on the top of the repository page.
- If you have the build permission,
  and no build task is set, the Create Build Task button is displayed on the top of the repository page.
  
  If a build task is set, the following statuses are displayed on the top of the repository page: Build task running , Building, Build failed, and Build successful.

Parent topic: Configuring a Repository

Previous topic: Viewing the Repository List

Next topic: Viewing Repository Homepage

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot