Configuring Project-Level Repository Settings

Constraints

Project manager or project administrator can configure project-level settings.

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** Project-level parameters
Parameter	Description
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.
Do not fork a repository	Optional. Once selected, no one can fork the repo in the project.
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. For details, see the example in Example.
Branch Name Rule	Optional. All branch names must match the regular expression with max. 500 characters. If this field is left blank, any branch name is allowed. The rules 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:. [ \ < ~ ^: ? ( ) ' " \|. The name of a new branch cannot be the same as that of an existing branch or tag.
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 name of a new tag cannot be the same as that of an existing branch or tag.