Change CI lint primary button style

What does this MR do and why?

Triggerred by @KevSlashNull's change in !81582 (merged), this will change the primary button style on the CI Lint page to match the button design guidelines[1] from the design system.

Screenshots or screen recordings

BEFORE	AFTER

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.

@gtsiolis

Thank you for your contribution to GitLab. We believe that everyone can contribute and contributions like yours are what make GitLab great!

• Our Merge Request Coaches will ensure your contribution is reviewed in a timely manner*.
• If you haven't, please set up a DANGER_GITLAB_API_TOKEN.
• You can comment @gitlab-bot label ~"group::" to add a group label.
• When you feel your MR (merge request) is ready for a review, just ask @gitlab-bot request_review and someone will take a look.
• If you are stuck, feel free to ask @gitlab-bot help or ping a Merge Request Coach.
• Read more on how to get help.

This message was generated automatically. You're welcome to improve it.

added Community contribution label

assigned to @gtsiolis

added 1 commit

• ae7db2f1 - Change CI lint primary button style

Compare with previous version

@pburdette @cngo could you take a look at this minor change?

requested review from @pburdette

added frontend label

requested review from @cngo and removed review request for @pburdette

approved this merge request

removed review request for @cngo

Allure report

allure-report-publisher generated test report for 18616974!

review-qa-reliable: test report
review-qa-smoke: test report

added UX label

Thanks for helping us improve the UX of GitLab, your contribution is appreciated! We have pinged UX team members, stay tuned for their feedback.

added devopsverify grouppipeline authoring sectionops labels

@nadia_sotnikova I think this belongs to your group, would you mind reviewing?

requested review from @nadia_sotnikova

approved this merge request

removed review request for @nadia_sotnikova

	2 Warnings
	Please add a merge request type to this merge request.
	You've made some app changes, but didn't add any tests. That's OK as long as you're refactoring existing code, but please consider adding any of the ~"type::tooling", ~"tooling::pipelines", ~"tooling::workflow", documentation, QA 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
frontend	Chad Woolley (@cwoolley-gitlab) (UTC-6)	Kushal Pandya (@kushalpandya) (UTC+5.5)
UX	Rayana Verissimo (@rayana) (UTC+1)	No maintainer available

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.

Generated by Danger

mentioned in merge request !82161 (closed)