Revert "Merge branch '8235-fix-code-owner-suggestion-plan' into '11-4-stable-ee'"
What does this MR do?
Reverts https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8248 which was merged directly into 11-4-stable-ee branch. This is normally done as part of merging preparation MRs, to avoid any inconsistencies (e.g. commit history, changelog) in the new patch release, I think it's better to revert this MR now and cherry-pick it as any other MR when preparing next patch release.
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
Tests added for this feature/bug -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process. -
EE specific content should be in the top level /eefolder -
For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?