Update notifications.md to be organized by type
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.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Marcin Sedlak-Jakubowski