- 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
Copied.
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.
|
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:
|
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.
|
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.
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
