Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
- Service Overview
- Getting Started
-
User Guide
- Overview
- Git Installation and Configuration
- Setting SSH Key or HTTPS Password for CodeArts Repo Repository
- Migrating Data to CodeArts Repo
- Creating a CodeArts Repo Repository
- Associating the CodeArts Repo Repository
- Cloning or Downloading Code from CodeArts Repo to a Local PC
- Using CodeArts Repo
- Configuring CodeArts Repo
- Submitting Code to the CodeArts Repo
- More About Git
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
- SSHKey
-
Repository
- Obtain files in the branch directory.
- Obtaining Warehouse Statistics
- Obtains image files of a specific branch in a repository.
- Modifying the Status of a Repository Referenced by a Pipeline
- Checks whether a user has the warehouse administrator permission.
- Sets whether a repository is in public or private state.
- Obtains the content of a specified file in a specified branch of a repository.
- Obtaining the List of Public Sample Templates
- Creating a repository
- Obtain the short ID of the repository based on the repository name and group name to combine the short ID with the URL of the submission details page corresponding to commitid.
- Queries the submission of a branch of a repository based on the group name and repository name.
- Querying the Branch of a Warehouse
- This API is used to query the submission of a branch of a warehouse based on the warehouse ID. More optional parameters are provided.
- Adding a Deployment Key
- Deleting a Repository Deployment Key
- Obtains the last submission statistics of the warehouse.
- Repository Statistics
- Delete repositories
- Check the repository creation status.
- Querying the Tag List of a Warehouse
- Adding a Tag
- Querying the Details of a Warehouse
- Obtains the number of submitted code lines.
- Download Repository
- Creating a Protection Branch
- Obtaining the Repository Branch List
- Obtaining the List of Warehouse Combination Requests
- Obtaining Warehouse Combination Request Details
- V2Project
- RepoMember
- Commit
- File
- User
- WebHook
- Project
- V2 Warehouse Management
- Discussion
- Application Examples
- Appendix
-
FAQs
-
Managing Repositories
- How Can I Set Multiple SSH Keys on My Computer?
- How Can I Prevent Unauthorized Code Replication?
- How Do I Upgrade TLS?
- Should I Set a Public SSH Key for Each Repository?
- Can All Users Upload and Download Code with the Same SSH Key?
- Will the System Remove Deleted Project Members from Repositories and SSH Keys Created by Them?
- How Can I Make a Repository Private or Public?
- SSH Function Upgraded
- Using Repositories
- Migrating Repositories
-
FAQs
- Why Can't I View Repositories Created by Other Project Members?
- Is There Any File Size Limit in Repositories?
- Can I Export the Statistics on Code Lines Committed by Members?
- How Do I Prevent Files Containing Secrets from Being Pushed to a Repository?
- Why Can't I See the Repository Synchronization Tab?
- Will Related Git Code Branches Be Automatically Deleted When the Creator of a Git Branch Is Deleted?
- What Do I Do If a Binary File Fails to Be Pushed to CodeArts Repo?
-
Git Issues
- How Does Git Identify Repository Administrators?
- How Do I Obtain the Path Where Downloaded Code Is Stored?
- How Do I Obtain the Code Repository Address?
- What Are Repository URLs Used for?
- Does CodeArts Repo Support SVN?
- Can I Decompress a Compressed Package Uploaded to a Cloud Repository?
- How Do I Clear, Save, and Change the Username and Password in Git?
-
Troubleshooting
- Private Key Is Lost
- SSH Key Already Exits
- Git Keeps Asking for Passphrase During Code Clone via SSH
- Password Incorrect During Code Clone via HTTPS
- Committed Files Cannot Be Found in the Cloud Repository
- Message "pathspec XXX did not match any files" Is Displayed
- Message "Transport Error: cannot get remote repository refs. XXX.git: cannot open git-upload-pack" Is Displayed
- Message "syntax error near unexpected token `newline'" Is Displayed
- Message "unable to auto-detect email address" Is Displayed
- Message "fatal:Authentication failed" Is Displayed
- Message "'origin' does not appear to be a git repository" Is Displayed
- Message "You are not allowed to push code to protected branches on this project" is Displayed
- Message "Not a git repository" Is Displayed
- Message "src refspec master does not match any" Is Displayed
- Message "destination path 'XXX' already exists and is not an empty directory" Is Displayed
- Message "The requested URL returned error: 401" Is Displayed
- Code Push Fails
- Code Pull Fails
- Message "fatal: refusing to merge unrelated histories" Is Displayed
- Message "SSL certificate problem" Is Displayed
-
Managing Repositories
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 Rules Extraction (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 two semicolons (;;).
- 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.