Update rails Banner component

changed milestone to %16.7

added UX UX Paper Cuts groupux paper cuts typemaintenance labels

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	`@hraghuvanshi` (UTC+5.5, 4.5 hours ahead of author)	`@sgarg_gitlab` (UTC+5.5, 4.5 hours ahead of author)
frontend	`@lorenzvanherwaarden` (UTC+1, same timezone as author)	`@jivanvl` (UTC-6, 7 hours behind author)
UX	`@esybrant` (UTC-6, 7 hours behind author)	Maintainer review is optional for UX

Please check reviewer's status!

Reviewer is available!
Reviewer is unavailable!

Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

changed the description

Allure report

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for f1bc8cec

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Monitor          | 8      | 0      | 0       | 0     | 8     | ✅     |
| Data Stores      | 22     | 0      | 0       | 0     | 22    | ✅     |
| Verify           | 32     | 0      | 0       | 0     | 32    | ✅     |
| Create           | 40     | 0      | 7       | 0     | 47    | ✅     |
| Govern           | 57     | 0      | 0       | 0     | 57    | ✅     |
| Plan             | 55     | 0      | 0       | 0     | 55    | ✅     |
| Package          | 0      | 0      | 1       | 0     | 1     | ➖     |
| Framework sanity | 0      | 0      | 1       | 0     | 1     | ➖     |
| Manage           | 0      | 0      | 1       | 0     | 1     | ➖     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 214    | 0      | 10      | 0     | 224   | ✅     |
+------------------+--------+--------+---------+-------+-------+--------+

added 1 commit

b650e17f - Update rails Banner component

Compare with previous version

added 1 commit

81f849c5 - Update rails Banner component

Compare with previous version

changed the description

added 1 commit

4d988b11 - Update rails Banner component

Compare with previous version

added 1 commit

ddbd71a9 - Update rails Banner component

Compare with previous version

added 1 commit

56ab68fd - Update rails Banner component

Compare with previous version

Hey @seggenberger Could you please review UX?

requested review from @seggenberger

Hey @wandering_person and @rcrespo3 Could you please review backend and frontend and help me with the pipeline error? It's ruby, but about the frontend, so IDK who can help me better

There is an error unexpected '!' after 'CHILD_SELECTOR', but the CSS class is 'gl-border-none!'. I don't know what options do I have

requested review from @wandering_person and @rcrespo3

added 1 commit

c620eb6a - Update rails Banner component

Compare with previous version

added 1 commit

f1bc8cec - Update rails Banner component

Compare with previous version

approved this merge request

@seggenberger, thanks for approving this merge request.

This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break master, a new pipeline will be started shortly.

Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.