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
Notifications
CodeArts Repo Notifications
To set notifications, choose Settings > General Settings > Notifications on the repository details page.
The settings take effect only for the repository configured.
Only the repository administrator and owner can view the page and have the setting permission.
Email Notification
If all notification types in the notification settings are disabled, the system sends an email notification to the creator or administrator by default when you perform the following operations:
- When a repository is created, an email notification is sent to the creator or administrator by default.
- When a non-repository member applies to join a repository, an email notification is sent to the creator by default.
- When a repository is frozen or closed, an email notification is sent to the creator or administrator by default.
- Freeze a repository: Send email notifications to the repository owner and administrators by default. This cannot be manually configured.
When a service is disabled or a repository is in arrears, the repository is frozen. No operation can be performed on the frozen repository.
Within 30 days after a repository is frozen, you can renew the repository or enable services to unfreeze the repository.
- Close a repository: Send email notifications to the repository owner and administrators by default. This cannot be manually configured.
Closing a repository is equivalent to permanently deleting the repository. When the repository is frozen for more than 30 days, the repository will be closed.
- Delete a repository: Send email notifications to the repository owner, administrator, committer, developer, and viewer. This can be manually configured.
- Capacity warning: This parameter is not enabled by default. You can manually set the capacity warning threshold as required. When the capacity of a single repository exceeds the threshold, the system emails the repository owner, administrators, committers, and developers. The warning email is sent only once unless you update the warning settings.
- Open: Push states of the merge request (including create and re-open) to specified roles by email. By default, the email notification is disabled. You can enable it to send email notifications to scorers, approvers, reviewers, and mergers.
- Update: Push code updates of the branch associated with the merge request to specified roles by email. By default, the email notification is disabled. You can enable it to send email notifications to scorers, approvers, or reviewers.
- Merge: Send email notifications to the MR creator by default. You can determine whether to also send an email notification to the merger.
- Review: Send email notifications to the MR creator by default. You can also disable the notification.
- Approve: Send email notifications to the MR creator by default. You can manually set not to send the notification.
- Comment: Send email notifications to the MR creator by default. You can also disable the notification.
- Resolve Comment: Send email notifications to the MR creator by default. You can manually set not to send the notification.
If no email notification is received, go to Notifications to check whether the email and email notifications are enabled.
If you want to know repository changes in other ways than emails, you can choose Service Integration > Webhooks and customize notifications in your own system (third-party system).
CodeArts Notifications
CodeArts provides configurable notifications. On the CodeArts homepage, click your username in the upper right corner. In the dialog box that is displayed, click This Account Settings to configure notifications.
Choose General Settings> Notifications. Enable or disable and email notifications, and change the email address for receiving notifications.
You can also set a Do-Not-Disturb (DND) period so that you will not receive email notifications within the specified period.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.