Dogfood reviewer roulette build as a GitLab native feature
Go with a boring solution and use what we already have. Leverage a combination of `codeowner` roles categories and use auto-assignees based on the code owners. Categories maybe backend/frontend/test roles. Essentially storing the maintainers roster in GitLab itself. * Gather all Reviewer Roulette usecases * Identify the source of maintainers and find a suitable mechanism in code owners. * Implement logic to automatically assign from code owners instead. * Incremental work for features that are not available via automatic assignment. * Adding a comment in the issue, maybe a thin logic in danger that only performs notification. #### Related epics * https://gitlab.com/groups/gitlab-org/-/epics/306 * https://gitlab.com/groups/gitlab-org/-/epics/1330
issue