Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Process of CodeArts Repo
- Purchasing CodeArts
- Accessing CodeArts Repo Homepage
- Environment and Personal Settings
- Migrating Code and Syncing a Repository
- Creating a Repository
- Viewing Activities
- Viewing Repository Statistics
- Configuring Repository Settings
- Hierarchical Repository Management
- Configuring a Repository
- Managing Repo Member Permissions
- Cloning or Downloading Code Repo to a Local PC
- Uploading Code Files to CodeArts Repo
- Developing a Workflow
- Creating and Configuring a CodeArts Project
- Committing Code to CodeArts Repo and Creating a Merge Request
- Managing Merge Requests
- Managing Code Files
- Security Management
- Best Practices
-
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.
E2E Settings
Repo uses this E2E tracing setting to log code merge reasons, such as implementing a requirement, fixing a bug, or completing a work item. Association is enabled by default.
Integrated Systems
It integrates with CodeArts Req and uses work items in CodeArts Req to associate with code commits.
The repositories of Kanban projects do not support E2E settings.
Integration Policies
(Optional) Specify available selection conditions when you associate with a work item.
Excluded States: States of work items that CANNOT be associated with.
Associable Types: Types of work items that can be associated with.
Applicable Branches: Branches to comply with preceding restrictions.
Automatic ID Rules Extraction
Automatic ID extraction rules (automatically extracting ticket numbers based on code commitment information) are as follows:
- ID Prefix: (Optional) A maximum of 10 prefixes are supported, for example, [Trouble ticket number or Requirement ticket number].
NOTE:
If ID Prefix, Separator, and ID Suffix are not empty, the automatic ticket number extraction function is enabled by default.
- Separator: (Optional) The default value is a semicolon (;).
- ID Suffix: (Optional) The default value is a newline character.
NOTE:
- The values of ID Prefix, Separator, and ID Suffix cannot be the same.
- If Separator is left empty, the values of ID Prefix and ID Suffix cannot be semicolon (;).
- If ID Suffix is left empty, the values of ID Prefix and Separator cannot be \n.
- The values of ID Prefix, Separator, and ID Suffix are matched in full character mode. Regular expressions are not supported.
Examples
- Configure E2E settings.
- Go to the target repository.
- Choose Settings > Service Integration > E2E Settings. The E2E Settings page is displayed.
- Configure the following integration policies and click Submit.
Applicable Branches: Select the target branch, for example, branch.
ID Prefix: user-defined prefix, for example, Incorporated requirements.
- Create a work item.
- Create a File.
- Go to the repository list page and click the name of the target repository.
- On the Code tab, click Create and choose Create File from the drop-down list box. The page for creating a file is displayed.
- Enter the following information, retain the default values for other parameters, and click OK.
File name: user-defined file name, for example, Sample_Code.
File content: user-defined file content.
Commit message: Enter the prefix and work item number in the E2E settings, for example, 708635317.
- Extract the ticket number when creating a merge request.
- Switch to the Merge Requests tab and click New.
- Select Dev as the source branch and master as the target branch, and click Next. The page for creating a merge request is displayed.
At this point, the work item is automatically extracted to the merge request.
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