GitLab Notification Emails
GitLab has a notification system in place to notify a user of events that are important for the workflow.
Notification settings
You can find notification settings under the user profile.
Notification settings are divided into three groups:
- Global settings
- Group settings
- Project settings
Each of these settings have levels of notification:
- Watch: Receive notifications for any activity.
- On Mention: Receive notifications when
@mentioned
in comments. - Participate: Receive notifications for threads you have participated in.
- Disabled: Turns off notifications.
- Custom: Receive notifications for custom selected events.
- Global: For groups and projects, notifications as per global settings.
Global Settings
Global settings are at the bottom of the hierarchy. Any setting set here will be overridden by a setting at the group or a project level.
Group or Project settings can use global
notification setting which will then use anything that is set at Global Settings.
Group Settings
Group settings are taking precedence over Global Settings but are on a level below Project or Subgroup settings:
Group < Subgroup < Project
This means that you can set a different level of notifications per group while still being able to have a finer level setting per project or subgroup. Organization like this is suitable for users that belong to different groups but don’t have the same need for being notified for every group they are member of. These settings can be configured on group page under the name of the group. It will be the dropdown with the bell icon. They can also be configured on the user profile notifications dropdown.
Project Settings
Project settings are at the top level and any setting placed at this level will take precedence of any other setting. This is suitable for users that have different needs for notifications per project basis. These settings can be configured on project page under the name of the project. It will be the dropdown with the bell icon. They can also be configured on the user profile notifications dropdown.
Notification events
Below is the table of events users can be notified of:
Event | Sent to | Settings level |
---|---|---|
New SSH key added | User | Security email, always sent. |
New email added | User | Security email, always sent. |
New user created | User | Sent on user creation, except for omniauth (LDAP) |
User added to project | User | Sent when user is added to project |
Project access level changed | User | Sent when user project access level is changed |
User added to group | User | Sent when user is added to group |
Group access level changed | User | Sent when user group access level is changed |
Project moved | Project members [1] | [1] not disabled |
Issue / Merge request events
In most of the below cases, the notification will be sent to:
- Participants:
- the author and assignee of the issue/merge request
- authors of comments on the issue/merge request
- anyone mentioned by
@username
in the issue/merge request title or description - anyone mentioned by
@username
in any of the comments on the issue/merge request …with notification level “Participating” or higher
- Watchers: users with notification level “Watch”
- Subscribers: anyone who manually subscribed to the issue/merge request
- Custom: Users with notification level “custom” who turned on notifications for any of the events present in the table below
Event | Sent to |
---|---|
New issue | |
Close issue | |
Reassign issue | The above, plus the old assignee |
Reopen issue | |
Due issue | Participants and Custom notification level with this event selected |
Change milestone issue | Subscribers, participants mentioned, and Custom notification level with this event selected |
Remove milestone issue | Subscribers, participants mentioned, and Custom notification level with this event selected |
New merge request | |
Push to merge request | Participants and Custom notification level with this event selected |
Reassign merge request | The above, plus the old assignee |
Close merge request | |
Reopen merge request | |
Merge merge request | |
Change milestone merge request | Subscribers, participants mentioned, and Custom notification level with this event selected |
Remove milestone merge request | Subscribers, participants mentioned, and Custom notification level with this event selected |
New comment | The above, plus anyone mentioned by @username in the comment, with notification level “Mention” or higher |
Failed pipeline | The author of the pipeline |
Successful pipeline | The author of the pipeline, if they have the custom notification setting for successful pipelines set |
New epic |
In addition, if the title or description of an Issue or Merge Request is changed, notifications will be sent to any new mentions by @username
as if they had been mentioned in the original text.
You won’t receive notifications for Issues, Merge Requests or Milestones created by yourself (except when an issue is due). You will only receive automatic notifications when somebody else comments or adds changes to the ones that you’ve created or mentions you.
If an open merge request becomes unmergeable due to conflict, its author will be notified about the cause. If a user has also set the merge request to automatically merge once pipeline succeeds, then that user will also be notified.
Email Headers
Notification emails include headers that provide extra content about the notification received:
Header | Description |
---|---|
X-GitLab-Project | The name of the project the notification belongs to |
X-GitLab-Project-Id | The ID of the project |
X-GitLab-Project-Path | The path of the project |
X-GitLab-(Resource)-ID | The ID of the resource the notification is for, where resource is Issue , MergeRequest , Commit , etc |
X-GitLab-Discussion-ID | Only in comment emails, the ID of the discussion the comment is from |
X-GitLab-Pipeline-Id | Only in pipeline emails, the ID of the pipeline the notification is for |
X-GitLab-Reply-Key | A unique token to support reply by email |
X-GitLab-NotificationReason | The reason for being notified. “mentioned”, “assigned”, etc |
X-GitLab-NotificationReason
This header holds the reason for the notification to have been sent out, where reason can be mentioned
, assigned
, own_activity
, etc. Only one reason is sent out according to its priority:
own_activity
assigned
mentioned
The reason in this header will also be shown in the footer of the notification email. For example an email with the reason assigned
will have this sentence in the footer: "You are receiving this email because you have been assigned an item on {configured GitLab hostname}"
GitLab Notification Emails的更多相关文章
- Jenkins + Ansible + Gitlab之gitlab篇
前言 持续交付 版本控制器:Gitlab.GitHub 持续集成工具:jenkins 部署工具:ansible 课程安排 Gitlab搭建与流程使用 Ansible环境配置与Playbook编写规范 ...
- 远程办公的GitLab开源的员工手册:涵盖了公司价值观,内部沟通交流指南,开发流程,如何开会,写作风格指南,如何报销,如何请假,线上办公工具推荐等方方面面
原文 :https://docs.gitlab.com.cn/ce/ 英文 :https://about.gitlab.com/handbook/ GitLab Community Edition G ...
- 在CentOS6.4上安装GitLab
1.Install and configure the necessary dependencies On CentOS 6 (and RedHat/Oracle/Scientific Linux 6 ...
- 二、CentOS 7安装部署GitLab服务器(解决邮箱发信问题)
一.环境安装(10.0.0) 1.安装依赖软件 yum -y install policycoreutils policycoreutils-python openssh-server openssh ...
- [转]gitlab ci/cd 发布
转自 https://meigit.readthedocs.io/en/latest/configure_gitlab_i18n_and_create_gitlab_ci_with_gitlab_ru ...
- ofbiz 本地化及邮件设置126邮箱
ofibz登陆功能有通过电子邮件找会密码的功能,但找回密码功能需要配置一个发送email的邮箱账号和smtp服务器的配置,具体配置如下: 1:在ofbiz数据库的表product_store_emai ...
- The Google Test and Development Environment (持续更新)
最近Google Testing Blog上开始连载The Google Test and Development Environment(Google的测试和开发环境),因为blogspot被墙,我 ...
- Linux 上使用 Gmail SMTP 服务器发送邮件通知
导读 假定你想配置一个 Linux 应用,用于从你的服务器或桌面客户端发送邮件信息.邮件信息可能是邮件简报.状态更新(如 Cachet).监控警报(如 Monit).磁盘时间(如 RAID mdadm ...
- galera cluster,mysql配置wsrep_notify_cmd参数,增加邮件告警
vi /usr/local/sunlight/wsrep_notify_cmd.sh chown mysql:mysql /usr/local/sunlight/wsrep_notify_cmd.s ...
随机推荐
- Selenium2+python自动化61-Chrome您使用的是不受支持的命令行标记:--ignore-certificate-errors
前言 您使用的是不受支持的命令行标记:--ignore-certificate-errors.稳定性和安全性会有所下降 selenium2启动Chrome浏览器是需要安装驱动包的,但是不同的Chrom ...
- 修改后无警告全面支持non-ARC以及ARC的OpenUDID
OpenUDID Open source initiative for a universal and persistent UDID solution for iOS. 首创的给iOS提供设备唯一标 ...
- java代码将e.printStackTrace()写入log4j文件异常信息
try { ... } catch (Exception e) { log.error( "failed!", e ); } 或者 try { ... } catch (Excep ...
- list去除重复数据
在java里面要想去除list中的重复数据可以使用两种方式实现: 1. 循环list中的所有元素然后删除重复 public static List removeDuplicate(List list) ...
- MiniGUI ial 移植指南
MiniGUI ial 移植指南 2.1 ial的定义 ial是一个通用的抽象输入接口,可以输入统一的数据的结构,也就是说在MiniGUI的核心代码里输入的数据的格式是固定的,不管输入设备是鼠标 还是 ...
- struts 2中为什么抽象包不能包含action?
struts 2中为什么抽象包不能包含action?麻烦写详细点!
- 结合实例详解"pure Virtual function called"
作者:阿波 链接:http://blog.csdn.net/livelylittlefish/article/details/9750593 (4年前的一篇文章,翻出来共享一下.) 本实例即为经典的讲 ...
- 渐进结构—条件生成对抗网络(PSGAN)
Full-body High-resolution Anime Generation with Progressive Structure-conditional Generative Adversa ...
- 巧妙使用div+css模拟表格对角线
首先声明: 这只是探讨一种CSS模拟表格对角线的用法,实际在工作中可能觉得这样做有点小题大作,这不是本主题讨论的重点.如果对此深以为然的朋友,请一笑过之... 有时在插入文档时,要用到表格对角线,常见 ...
- Android -- Fragment注意事项
ViewPager+Fragment 让Fragment成为ViewPager的一页时,FragmentManager会一直保存管理创建好了的Fragment,即使当前不是显示的这一页,Fragmen ...