Add group assignment for Solutions Architecture
What does this MR do and why?
Adds a group assignment for Solutions Architecture to the TW codeowners rake task.
This will make pages in the Solutions Architecture
group, as designated by docs markdown front matter, require a review from a member of @gitlab/solutions-architecture
for merge.
Related to #430270 (closed)
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
assigned to @sarahgerman
mentioned in issue #430270 (closed)
mentioned in issue Taucher2003/reporting#208 (closed)
added 1 commit
- 81f62b1e - Add group assignment for Solutions Architecture
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
changed milestone to %16.6
requested review from @sselhorn
1 Warning Labels missing: please ask a reviewer or maintainer to add backend to this merge request. 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 @hustewart
(UTC-5, 1 hour ahead of author)
@drew
(UTC+0, 6 hours ahead of author)
/lib/tasks/gitlab/tw/codeowners.rake
Reviewer review is optional for /lib/tasks/gitlab/tw/codeowners.rake
@kpaizee
(UTC+2, 8 hours ahead of 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
DangerEdited by Ghost User@sselhorn
, thanks for approving this merge request.This is the first time the merge request has been approved. To ensure full test coverage, a new pipeline will be started shortly.
For more info, please refer to the following links:
added pipeline:mr-approved label
enabled an automatic merge when the pipeline for 0a84d9f1 succeeds
Allure report
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for 81f62b1eexpand test summary
+-----------------------------------------------------------------------+ | suites summary | +------------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +------------------+--------+--------+---------+-------+-------+--------+ | Create | 40 | 0 | 6 | 0 | 46 | ✅ | | Govern | 48 | 0 | 0 | 0 | 48 | ✅ | | Verify | 32 | 0 | 0 | 0 | 32 | ✅ | | Plan | 55 | 0 | 0 | 0 | 55 | ✅ | | Data Stores | 22 | 0 | 0 | 0 | 22 | ✅ | | Monitor | 4 | 0 | 0 | 0 | 4 | ✅ | | Manage | 0 | 0 | 1 | 0 | 1 | ➖ | | Package | 0 | 0 | 1 | 0 | 1 | ➖ | | Framework sanity | 0 | 0 | 1 | 0 | 1 | ➖ | +------------------+--------+--------+---------+-------+-------+--------+ | Total | 201 | 0 | 9 | 0 | 210 | ✅ | +------------------+--------+--------+---------+-------+-------+--------+
mentioned in commit 08da0be6
added workflowstaging-canary label and removed workflowin dev label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-production label and removed workflowproduction label
added releasedcandidate label