Notifications
CodeArts Repo Notifications
To set notifications, choose
on the repository details page.The settings take effect only for the repository configured.
All repository members can view this page. For details about whether a repository member has repository setting permissions, refer to the Permissions page.
Email Notification
![](https://support.huaweicloud.com/intl/en-us/usermanual-codeartsrepo/public_sys-resources/note_3.0-en-us.png)
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 project administrator by default.
- When a non-repository member applies to join a repository, an email notification is sent to the repository owner by default.
- When a repository is frozen or closed, an email notification is sent to the repository owner or project administrator by default.
- Delete a repository: Send email notifications to the repository owner, project administrators, project managers, committers, developers, and viewers. This can be manually configured.
- Capacity warning: The default threshold is 90%. You can change it as required. When the capacity of a single repository exceeds the threshold, the system sends email notifications to the repository owner, project administrators, project managers, 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, email notifications are sent to scorers, approvers, reviewers, and mergers. You can also disable the notifications for specific roles.
- Update: Push code updates of the branch associated with the merge request to specified roles by email. By default, email notifications are sent to scorers, approvers, and reviewers. You can also disable the notifications for specific roles.
- 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 also disable 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 also disable the notification.
![](https://support.huaweicloud.com/intl/en-us/usermanual-codeartsrepo/public_sys-resources/note_3.0-en-us.png)
If no email notification is received, go to Notifications to check whether the email notification is 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).
WeCom notification
Click WeCom. The WeCom notification setting page is displayed.
- Webhook URL: Webhook URL of the robot added by the CodeArts Repo member group. This parameter is mandatory, and can contain a maximum of 500 characters. Developers can send an HTTP POST request to this address to send messages to the member group.
A webhook URL pushes WeCom notifications to the administrative robot. A maximum of 20 notifications can be sent per minute. More notifications will be limited by WeCom, causing data loss.
The creator of a group robot can view the robot information to obtain the webhook URL.
- On your mobile phone, click the three dots in the upper right corner, click the group robot, and select the corresponding robot to obtain the webhook URL.
- On your computer, click the group member list, select the corresponding robot to obtain the webhook address from the details.
- Delete a repository: Push WeCom notifications to the administrative robot. You can also disable the notification.
- Capacity warning: If this option is selected, the threshold is 90% by default. You can also select another threshold from the drop-down list box. When the repository capacity reaches the threshold, WeCom notifications will be pushed to the administrative robot. You can also disable the notification.
Merge request status change
- Open: Push states of the merge request (including create and re-open) to the administrative robot by WeCom. You can also disable the notification.
- Update: Push code updates of the source branch to the administrative robot by WeCom. This parameter is disabled by default.
- Merge: Push new merge requests to the administrative robot by WeCom. You can also disable the notification.
Merge request review and approval
- Review: Push review status (including passed and canceled) to the administrative robot by WeCom. This parameter is disabled by default. You can enable the notification.
- Approve: Push approval status (including passed, rejected, and canceled) to the administrative robot by WeCom. This parameter is disabled by default. You can enable the notification.
Merge request review comments
- Create: Push new reviews or comments to the administrative robot by WeCom. You can also disable the notification. When replying to the reviews or comments, no WeCom notification will be sent to the administrative robot.
- Resolve: Push resolved reviews or comments to the administrative robot by WeCom. This parameter is disabled by default. When the review or comment status is Unresolved, no WeCom notification will be sent to the administrative robot.
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.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot