Update badge in accessibility issue body
What does this MR do and why?
Describe in detail what your merge request does and why.
A small MVC for: #344302 (closed) where we make badges in app/assets/javascripts/reports/accessibility_report/components/accessibility_issue_body.vue Pajamas-compliant.
Screenshots or screen recordings
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
- Enable GDK local merge widget
- Set up local accessibility report scanning:
- Create a merge with accessibility issues
- Confirm "New" Badge
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.
Merge request reports
Activity
changed milestone to %14.8
added OKR-FY24Q2 Pajamas devopscreate frontend groupeditor [DEPRECATED] labels
requested review from @markrian
assigned to @oregand
Resolved by Mark FlorianLast one for today!
- Last reply by Mark Florian
added workflowin review label
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 frontend Robert Hunt ( @rob.hunt) (UTC+0, 6 hours ahead of@oregand)Paul Slaughter ( @pslaughter) (UTC-6, same timezone as@oregand)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. 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-reviewjob that generated this comment.Generated by
Bundle size analysis [beta]
This compares changes in bundle size for entry points between the commits 2f009075 and 0f35af40
Entrypoint / Name Size before Size after Diff Diff in percent average 3.67 MB 3.67 MB - -0.0 % mainChunk 2.29 MB 2.29 MB - 0.0 %
Note: We do not have exact data for 2f009075. So we have used data from: b6cc01f2.
The target commit was too new, so we used the latest commit from master we have info on.
It might help to rerun thebundle-size-reviewjob
This might mean that you have a few false positives in this report. If something unrelated to your code changes is reported, you can check this comparison in order to see if they caused this change.Please look at the full report for more details
Read more about how this report works.
Generated by
added sectiondev label
@markrian, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline has been started.
For more info, please refer to the following links:
enabled an automatic merge when the pipeline for bef45cc1 succeeds
added typemaintenance label
Allure report
allure-report-publishergenerated test report for 0f35af40!review-qa-reliable:
review-qa-smoke:mentioned in commit 89b2276b
added workflowstaging-canary label and removed workflowin review label
added workflowstaging label and removed workflowstaging-canary label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
added releasedcandidate label
mentioned in merge request kubitus-project/kubitus-installer!677 (merged)
added releasedpublished label and removed releasedcandidate label
