Remove "Learn more." link from coverage check in MR approval rules

added pipelinetier-1 label

Thanks for your contribution to GitLab @peterhdangg!

If you need help, page a coach by clicking here or come say hi on Discord.
When you're ready, request a review by clicking here.
We welcome AI-generated contributions and offer complimentary access to GitLab Duo!
To add labels to your merge request, comment @gitlab-bot label ~"label1" ~"label2".

This message was generated automatically. Improve it or delete it.

added Community contribution workflowin dev labels

assigned to @peterhdangg

changed the description

This merge request will be counted as part of the running Hackathon!

Find yourself in the Hackathon Leaderboard or check out the Hackathon page for more information!

This message was generated automatically. Improve it or delete it.

added Hackathon label

added linked-issue label

	3 Warnings
	d7bee289: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.
	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 maintenancepipelines, maintenancerefactor, maintenanceworkflow, maintenanceperformance, documentation, QA labels.
	Labels missing: please ask a reviewer or maintainer to add frontend to this merge request.

1 Message

CHANGELOG missing:

If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog.

If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
frontend	`@thutterer` (UTC+1)	`@ohoral` (UTC+1)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

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

Generated by Danger

@gitlab-bot ready

Posted via contributors.gitlab.com.

added workflowready for review label and removed workflowin dev label

Hi Coach @toon, this Community contribution is ready for review or needs your coaching.

Do you have capacity and domain expertise to review this? If not, find one or more reviewers and assign to them.
If you've reviewed it, add the workflowin dev label if these changes need more work before the next review.
Please ensure the group's Product Manager has validated the linked issue.

This message was generated automatically. Improve it or delete it.

requested review from @toon

mentioned in issue gitlab-org/quality/triage-reports#21995 (closed)

added bugux devopscreate docsfeature typebug labels

added sectiondev label

mentioned in issue gitlab-org/quality/triage-reports#22003 (closed)

mentioned in issue gitlab-org/quality/triage-reports#22004 (closed)

added groupsource code label

added Category:Source Code Management label

changed milestone to %17.9

approved this merge request

added pipeline:mr-approved label

added pipelinetier-2 label and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3.

Before you set this MR to auto-merge, please check the following:

You are the last maintainer of this merge request
The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.

@zcuddy Can you please review and merge this small cosmetic cleanup?

requested review from @zcuddy and removed review request for @toon

Solid work @peterhdangg!

Just one small suggestion to fully cleanup the link usage in this file!

Back to you

added 1 commit

d7bee289 - removed unused vue injection

Compare with previous version

resolved all threads

Great work @peterhdangg, thanks for removing that injection!

frontend approved and MWPS

sorry for the lack of update, slipped my mind while waiting for pipeline to pass. thank you for merging!

approved this merge request

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-2 label

enabled automatic add to merge train when checks pass

added frontend label

3 Warnings

d7bee289: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.

The master pipeline status page reported failures in

rubocop

If these jobs fail in your merge request with the same errors, then they are not caused by your changes.
Please check for any on-going incidents in the incident issue tracker or in the #master-broken Slack channel.

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 maintenancepipelines, maintenancerefactor, maintenanceworkflow, maintenanceperformance, documentation, QA labels.

1 Message

CHANGELOG missing:

If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog.

If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
frontend	`@thutterer` (UTC+1)	`@ohoral` (UTC+1)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

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

Generated by Danger

Bundle size analysis [beta]

This compares changes in bundle size for entry points between the commits 9011c792 and d7bee289

Special assets

Entrypoint / Name	Size before	Size after	Diff	Diff in percent
average	4.43 MB	4.43 MB	-	0.0 %
mainChunk	3.29 MB	3.29 MB	-	0.0 %

Note: We do not have exact data for 9011c792. So we have used data from: 1cf60f9e.
The intended commit has no webpack pipeline, so we chose the last commit with one before it.

Please look at the full report for more details

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-cng: test report for d7bee289

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Create      | 143    | 0      | 19      | 0     | 162   | ✅     |
| Govern      | 84     | 0      | 10      | 0     | 94    | ✅     |
| Plan        | 86     | 0      | 8       | 0     | 94    | ✅     |
| Verify      | 53     | 0      | 19      | 0     | 72    | ✅     |
| Package     | 29     | 0      | 15      | 0     | 44    | ✅     |
| Data Stores | 33     | 0      | 10      | 0     | 43    | ✅     |
| Monitor     | 8      | 0      | 12      | 0     | 20    | ✅     |
| Configure   | 0      | 0      | 3       | 0     | 3     | ➖     |
| Manage      | 1      | 0      | 9       | 0     | 10    | ✅     |
| Growth      | 0      | 0      | 2       | 0     | 2     | ➖     |
| Fulfillment | 2      | 0      | 7       | 0     | 9     | ✅     |
| Secure      | 2      | 0      | 5       | 0     | 7     | ✅     |
| Ai-powered  | 0      | 0      | 2       | 0     | 2     | ➖     |
| Release     | 5      | 0      | 1       | 0     | 6     | ✅     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
| ModelOps    | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 448    | 0      | 123     | 0     | 571   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

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

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Monitor     | 8      | 0      | 12      | 0     | 20    | ✅     |
| Create      | 138    | 0      | 20      | 0     | 158   | ✅     |
| Plan        | 82     | 0      | 8       | 0     | 90    | ✅     |
| Manage      | 1      | 0      | 9       | 0     | 10    | ✅     |
| Verify      | 52     | 0      | 20      | 1     | 72    | ✅     |
| Govern      | 79     | 0      | 13      | 0     | 92    | ✅     |
| Data Stores | 33     | 0      | 10      | 0     | 43    | ✅     |
| Package     | 24     | 0      | 14      | 0     | 38    | ✅     |
| Fulfillment | 2      | 0      | 7       | 0     | 9     | ✅     |
| Configure   | 0      | 0      | 3       | 0     | 3     | ➖     |
| Growth      | 0      | 0      | 2       | 0     | 2     | ➖     |
| Secure      | 4      | 0      | 3       | 0     | 7     | ✅     |
| Ai-powered  | 0      | 0      | 2       | 0     | 2     | ➖     |
| Release     | 5      | 0      | 1       | 0     | 6     | ✅     |
| ModelOps    | 0      | 0      | 1       | 0     | 1     | ➖     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 430    | 0      | 125     | 1     | 555   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

started a merge train

merged

Hi @peterhdangg

See where you rank! Check your spot on the contributor leaderboard and unlock rewards.

How was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

React with a or a on this comment to describe your experience.
Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

As a benefit of being a GitLab Community Contributor, you have access to GitLab Duo, our AI-powered features. With Code Suggestions, Chat, Root Cause Analysis and more AI-powered features, GitLab Duo helps to boost your efficiency and effectiveness by reducing the time required to write and understand code and pipelines. Visit the GitLab Duo documentation to learn more about the benefits.

Thanks for your help!

This message was generated automatically. Improve it or delete it.