Remove unused available_namespaces_controller

changed milestone to %15.8

added backend maintenanceremoval typemaintenance + 1 deleted label

assigned to @xanf

added devopsfoundations sectiondev labels

1 Message

CHANGELOG missing:

If you want to create a changelog entry for GitLab FOSS, add the Changelog trailer to the commit message you want to add to the changelog.

If you want to create a changelog entry for GitLab EE, also add the EE: true trailer to your commit message.

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

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	Gregory Havenga (`@ghavenga`) (UTC+2, same timezone as `@xanf`)	Steve Abrams (`@sabrams`) (UTC-7, 9 hours behind `@xanf`)

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

Allure report

allure-report-publisher generated test report!

e2e-review-qa: test report for 49eddd24

expand test summary

+-------------------------------------------------------------+
|                       suites summary                        |
+--------+--------+--------+---------+-------+-------+--------+
|        | passed | failed | skipped | flaky | total | result |
+--------+--------+--------+---------+-------+-------+--------+
| Manage | 34     | 0      | 3       | 1     | 37    | ❗     |
+--------+--------+--------+---------+-------+-------+--------+
| Total  | 34     | 0      | 3       | 1     | 37    | ❗     |
+--------+--------+--------+---------+-------+-------+--------+

@nicolasdular could you please review this one?

requested review from @nicolasdular

approved this merge request

requested review from @stanhu and removed review request for @nicolasdular

@nicolasdular, thanks for approving this merge request.

This is the first time the merge request is 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

approved this merge request

resolved all threads

merged

@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 6 hours ago, and finished more than 2 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 merge when pipeline succeeds.

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.