Create framework for inline notifications in MR diff
Problem to solve
The Code Quality team is building backend capability (gitlab#322689 (closed)) to add inline annotations in the MR diff, and Static Analysis is going to be adding our findings (SAST and Secret Detection) in there as well. How might we create a framework so that other teams can utilize this functionality while accommodating for scalability and flexibility, and all possible states (e.g. empty state and many findings one and the possibility of there being too much "noise")?
Why a framework?
-
This is one of the most visible areas of the product, used by millions of people every month.
-
For the organization, this can be framed as increasing velocity, increasing Stages per Organization, increasing MAU, increasing SUS, increasing code quality, and decreasing technical and UX debt.
What this looks like
-
Create design guidelines that allows these annotations to be scalable so other groups can use them. How can we prepare for the future and the unknowns?
-
Document in our Pajamas Design System
- Show closed items