Help Center/ CodeArts Repo/ User Guide/ Configuring Project-Level Settings for CodeArts Repo/ Configuring Project-Level Repository Settings
Updated on 2025-07-24 GMT+08:00
View PDF
Share

Configuring Project-Level Repository Settings

Constraints

Project manager or project administrator can configure project-level settings. For details, see Configuring Project-Level Permissions.

Configuring the Repository Settings

If you want to set the same settings for all repositories in a project, click the project on the CodeArts Repo homepage, and choose Settings > Repository Management > Repository Settings. Set parameters by referring to Table 1.

Table 1 Repository settings description

Parameter

Description

Example Value

Force inherit

Optional. Once selected, all repository groups and repositories in the project use the following settings and cannot be changed. Exercise caution when selecting this option.

Select Force inherit.

Do not fork a repository

Optional. Once selected, no one can fork the repo in the project.

Select Do not fork a repository. After this parameter is set, access any repository in the project and click Fork in the upper right corner. A dialog box is displayed in the upper right corner.

Pre-merge

Optional. Once this is selected, the server automatically generates the pre-merge code of the MR. Compared with running commands on the client, this operation is more efficient and simple, and the build result is more accurate. This option applies to scenarios that have strict requirements on real-time build.

Select Pre-merge. For details, see Example.

Branch Name Rule

Optional. After you enter a rule, all branch names must match the regular expression with max. 500 characters. If this field is left blank, any branch name is allowed. You must meet the following tag naming rules:

  • Max. 500 characters.
  • Do not start with -, refs/heads/ or refs/remotes/ nor end with . / .lock. Spaces and the following characters are not supported:. [ \ < ~ ^: ? ( ) ' " |.
  • Must be unique.

Branch_[a-zA-Z0-9_]+: indicates that all branch names in the project must start with Branch_ and can match any combination of uppercase or lowercase letters, digits, and underscores (_).

Tag Name Rule

Optional. All tag names must match the regular expression specified by this parameter. If this field is left blank, any tag name is allowed. The basic tag naming rules must be met.

  • Max. 500 characters.
  • Do not start with -, refs/heads/ or refs/remotes/ nor end with . / .lock. Spaces and the following characters are not supported:. [ \ < ~ ^: ? ( ) ' " |.
  • The tag name must be unique.

Tag_[a-zA-Z0-9_]+: indicates that all tag names must start with Tag_ and can match any combination of uppercase or lowercase letters, digits, and underscores (_).

Related Document

  • If the error message indicating a branch name does not match the rule is displayed when a branch is created, the new branch name Test_Branch does not match the branch name rule Branch_. Choose Settings > Repository Management > Repository Settings to view the latest branch name rule and create a branch based on it.
  • If the error message indicating a tag name does not match the rule is displayed when a tag is created, the new tag name Test_Tag does not match the tag name rule Tag_. Choose Settings > Repository Management > Repository Settings to view the latest tag name rule and create a tag based on it.