Adjust tests to api admin mode (12)

Thank you for your contribution to GitLab. Please refer to the contribution flow documentation for a quick overview of the process, and the merge request (MR) guidelines for the detailed process.

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help, feel free to post @gitlab-bot help or initiate a mentor session on Discord. Read more on how to get help.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

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

added Community contribution workflowin dev labels

assigned to @TrueKalix

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	Tiger Watson (`@tigerwnz`) (UTC+11)	Alex Pooley (`@alexpooley`) (UTC+8)

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-review job that generated this comment.

Generated by 🚫 Danger

changed title from Adjust tests to api admin mode to Adjust tests to api admin mode (12)

@gitlab-bot ready

added workflowready for review label and removed workflowin dev label

@terrichu, this Community contribution is ready for review.

Do you have capacity and domain expertise to review this? We are mindful of your time, so if you are not able to take this on, please re-assign to one or more other reviewers.
Add the workflowin dev label if the merge request needs action from the author. This message was generated automatically. You're welcome to improve it.

requested review from @terrichu

added groupthreat insights maintenancerefactor typemaintenance labels

added devopsgovern sectionsec labels

approved this merge request

@TrueKalix thanks for the contribution 😄 Everything LGTM, @bwill would you mind taking maintainer review for this MR (I believe your team is DRI for one or more of the APIs in this MR) 🙇

requested review from @bwill and removed review request for @terrichu

👋 @terrichu, thanks for approving this merge request.

This is the first time the merge request is approved. To ensure full test coverage, please start a new pipeline before merging.

For more info, please refer to the following links:

added pipeline:mr-approved label

added backend 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
backend	Tiger Watson (`@tigerwnz`) (UTC+11)	Alex Pooley (`@alexpooley`) (UTC+8)

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-review job that generated this comment.

Generated by 🚫 Danger

changed milestone to %15.11

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

changed the description

added 1 commit

33257826 - Adjust tests to api admin mode

Compare with previous version

added workflowin dev label and removed workflowready for review label

removed review request for @bwill

added 1 commit

7b90062b - Adjust tests to api admin mode

Compare with previous version

resolved all threads

approved this merge request

enabled an automatic merge when the pipeline for f3654e3c succeeds

merged

mentioned in commit d72bacd6

@TrueKalix, 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.

Interested in learning more tips and tricks to solve your next challenge faster? Subscribe to the GitLab Community Newsletter for contributor-focused content and opportunities to level up.

Thanks for your help! ❤

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