Configuring Merge Request Notifications

Updated on 2024-11-22 GMT+08:00

View PDF

You can push notifications about repositories and merge requests through emails or WeCom, and enable either or both of these two modes as needed. Repository members can view this page. Only roles with the Set permission can set repository notifications.

For details about how to configure email notifications, see Configuring Email Notifications.
For details about how to configure WeCom notifications for repositories, see Table 2.

Configuring Email Notifications

**Table 1** Parameters for email notifications
Parameter	Description
Repository	Optional. Set the email notification you want to receive. Four options are available. By default, Freeze Repo and Close Repo are selected and cannot be changed. If a repo is frozen or closed, an email will be sent to the repo owner and project administrator. The other two options are as follows, and you can select when to receive email notifications: Delete Repo: When a member deletes the repository. Capacity Warning: When the capacity usage exceeds the threshold. You can select 60%, 80%, or 90% from the drop-down list.
Merge Request	Optional. You can select the following options as needed. Open: When a merge request is created or re-created, an email will be sent to the selected roles. By default, the following roles are selected: Scorer, Approver, Reviewer, and Merger. Update: When the code of the branch associated with the merge request is updated, an update email is pushed. The following roles are selected by default: Scorer, Approver, and Reviewer. Merge: An email will be pushed when a merge request is committed. The MR creator is selected by default. You can also select Merger. Review: An email will be sent to notify the merge request review. The MR creator is selected by default. Approve: An email will be sent to notify the merge request approval. The MR creator is selected by default. Comment: The email of new review comments will be sent to the selected role. The MR creator is selected by default. Resolve Comment: An email will be sent to the selected role to resolve the review comments. The MR creator is selected by default.

NOTE:

If you have enabled the email notification in CodeArts Repo but cannot receive any email notification, go to CodeArts notifications to check whether the email configuration and email notification are enabled.

Configuring WeCom Notification Settings for the Repository

**Table 2** Parameters for setting WeCom notifications
Parameter	Description
Webhook URL	Mandatory. Used to identify webhook address of the robot added to the CodeArts Repo member group with a maximum of 500 characters.
Repository	Optional. Select the following two options based on your need. By default, the following two options are selected. You can also select the email recipients. Delete Repo: When a member deletes the repository. Capacity Warning: When the capacity usage exceeds the threshold. You can select 60%, 80%, or 90% from the drop-down list.
Merge Request	Optional. You can select the following options as needed. Status Change Notifications are pushed through the WeCom bot when the MR is opened, updated, or merged. By default, the following options are selected: Open and Merge. Review and Approval: You can select Review or Approve. Review Comments: By default, Comment is selected. You can also select Resolved comment.