Skip to content

Update notifications.md to be organized by type

Alexander Turinske requested to merge aturinske-master-patch-44532 into master

Marcin: If you're a person from the future, reading this because a row in the table is incorrect, it might have been empty before this edit, and Alexander and I made an educated guess what it should say.

What does this MR do and why?

Describe in detail what your merge request does and why.

Update notifications.md to be organized by type

  • separate by epic/issue/merge request/pipeline
  • fill in any empty columns

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After
https://docs.gitlab.com/ee/user/profile/notifications.html#notification-events-on-issues-merge-requests-and-epics#notification-events-on-issues-merge-requests-and-epics image https://main-ee-107322.docs.gitlab-review.app/ee/user/profile/notifications.html#notification-events-on-issues-merge-requests-and-epics image

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Navigate to https://docs.gitlab.com/ee/user/profile/notifications.html#notification-events-on-issues-merge-requests-and-epics

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Marcin Sedlak-Jakubowski

Merge request reports