Add badge image
What does this MR do and why?
GitLab has officially been awarded our CHAOSS DEI badge. This MR adds the image of the badge into our DEI Project Statement file.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Merge request reports
Activity
assigned to @daniel-murphy
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 @syarynovskyi
(UTC+2, 7 hours ahead of author)
@pgascouvaillancourt
(UTC-5, same timezone as author)
Please check reviewer's status!
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- Resolved by 🤖 GitLab Bot 🤖
Proper labels assigned to this merge request. Please ignore me.
@daniel-murphy - please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request. Edited by 🤖 GitLab Bot 🤖
changed milestone to %16.9
added contributorgrowthDEI label
added typemaintenance label
requested review from @stanhu
- Resolved by Suzanne Selhorn
@stanhu
, 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.
added pipeline:mr-approved label
revoked approvals from @stanhu by pushing to the branch
added Technical Writing label
requested review from @stanhu
@stanhu When I moved folder locations, it removed your approval. Would you mind doing the merge?
- A deleted user
added frontend label
- Resolved by Suzanne Selhorn
added maintenancerefactor label
removed review request for @sselhorn
- Resolved by Suzanne Selhorn
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for da490854expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Verify | 31 | 0 | 0 | 0 | 31 | ✅ | | Manage | 0 | 0 | 1 | 0 | 1 | ➖ | | Create | 49 | 0 | 10 | 0 | 59 | ✅ | | Plan | 53 | 0 | 0 | 0 | 53 | ✅ | | Data Stores | 31 | 0 | 1 | 0 | 32 | ✅ | | Package | 15 | 0 | 1 | 0 | 16 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Monitor | 7 | 0 | 0 | 0 | 7 | ✅ | | Govern | 65 | 0 | 1 | 0 | 66 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 258 | 0 | 14 | 0 | 272 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
enabled an automatic merge when all merge checks for da490854 pass
@stanhu, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 4 hours ago, you should:
- Ensure the merge request is not in Draft status.
- Start a pipeline (especially important for Community contribution merge requests).
- Set the merge request to auto-merge.
This is a guideline, not a rule. Please consider replying to this comment for transparency.
This message was generated automatically. You're welcome to improve it.
mentioned in commit 4316170f
mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#5078 (closed)
mentioned in commit e6f0be0f
mentioned in merge request !142890 (merged)
@daniel-murphy apologies but
this MR inadvertently lead to a broken spec in gitlab-org/quality/engineering-productivity/master-broken-incidents#5078 (closed). We are reverting it in !142890 (merged) to unblock developers.Edited by Sylvester Chin@schin1 @stanhu Thanks for that update! What is the best and fastest way to get this change merged again without disrupting things? GitLab and CHAOSS are announcing this live on Monday and the GitLab article will link back to this file to show verification of our DEI badge. Would like to have this merged today ahead of that :-)
cc: @esalvadorp @nick_vh
@schin1 @stanhu Created new MR to add the image in using the CMS instead: !142925 (merged)
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
mentioned in merge request !142925 (merged)
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
mentioned in commit 1f2c9a80
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added pipelinetier-3 label