Kernel changeset Notifications
GitLab-based workflows provide several notification options to code maintainers and interested parties to be notified of merge requests. These options include GitLab Email and ‘@’ notifications, GitLab RSS, GitLab CODEOWNERS, and CKI.
By default users will receive notifications for GitLab ‘@’ mentions and notifications for any Merge Request or Issue they open. Code Maintainers should review the Code Owners section below, and contributors interested in specific files or directories should look at the Subsystem Labels section.
GitLab Email and ‘@’ mentions
GitLab has a highly-tunable email notification system. Emails are sent to participants (contributors, reviewers, and commenters) of merge requests. Similar to Twitter and other messaging platforms, additional participants can be notified via ‘@’ mentions. For example, to notify username rhuser a comment could be added to the merge request with ‘@rhuser’. This action would result in an email being sent to rhuser with the comment and a link to the merge request.
Webhooks
The kernel-webhooks project adds GitLab Reviewers and labels to Merge Requests through several methods.
Subsystem Labels
The documentation project’s owners.yaml file contains information about each kernel subsystem, including a label for each subsystem, and the files that belong to each subsystem. When a contributor submits a merge request, the webhooks interpret the information from owners.yaml to apply Subsystem Labels to the merge request. Users can subscribe to labels at either the group or project level. A user may subscribe to a label at the group level and then they will receive an email notification when that label is added to an MR in any of the group’s projects. Or for more control a user may subscribe to labels at the project level. Kernel-ark is the exception where Subsystem labels are only defined at the project level so must be subscribed to there.
Kernel group Subsystem labels
Project Subsystem labels
Ack/Nack
The Ack/Nack webhook (commonly referred to as the Ack/Nack bot) uses maintainer and reviewer information from the documentation project’s owners.yaml file. The Ack/Nack webhook adds all listed maintainers and reviewers as GitLab Reviewers to matching Merge Requests.
GitLab RSS
Each GitLab project provides a variety of RSS feeds that users can subscribe to, and RSS link buttons can be found on the main panel. For example, the RSS feed button to subscribe to merge request notifications is highlighted in a red circle on this screenshot of the centos-stream-9 merge request page,
Configuration of RSS feeds is dependent on your choice of browser and choice of RSS feed reader. Firefox users have also reported requiring having to copy-and-paste GitLab RSS links into many popular RSS readers.
GitLab provides RSS feeds and cannot be modified by Red Hat.
Code Owners
TBD - have to implement this.
GitLab has a review mechanism that will automatically assign required reviewers for code changes called Code Owners that is similar in functionality to the kernel’s MAINTAINERS file & scrits/get_maintainers.pl. Code Owners allows project maintainers to assign ownership of files or directories to specific contributors or groups of contributors. Emails notifications are sent to these contributors alerting them to MRs that modify their areas of responsibility within the kernel.
Code Owners are listed in the project’s .gitlab/CODEOWNERS file, and is typically referred to as simply CODEOWNERS. Like any other changes made to the kernel, modifications to CODEOWNERS must be made through a merge request to the kernel project.
Self Scripted Solutions
Contributors are encouraged to write and submit their own scripts to the kernel-tools project.
GitLab Email Bridge
The GitLab Email Bridge mimics the traditional email-based review process by converting GitLab merge request changesets and comments into email. The Email Bridge is only temporary to assist during the transition between the email-review process and the GitLab review process.* Users of the Email Bridge should not depend it’s output in the long-term. *
The Email Bridge for RHEL kernels will be taken out of service on February 22, 2022.
The table below contains configured Email Bridge projects and the mailing list where the Email Bridge sends notifications.
| Project | Email list |
|---|---|
Adding additional metadata to Email Bridge email
Users can add metadata to the “cover-letter” email sent by the Email Bridge by adding additional metadata in brackets to the merge request title.
For example, creating a merge request with title “[BZ123456] This interesting patch” will result in an Email Bridge cover letter of “[RHELX.Y][BZ 123456] This interesting patch”.