Loading
chore: update Danger roulette project key to client-go
What does this MR do and why?
Updates the Dangerfile to pass client-go instead of gitlab-api-client-go to Gitlab::Dangerfiles.for_project, so this project's Danger reviewer roulette matches the renamed roulette key.
Why: community MRs on this project currently get a review-request note that pings a random available MR coach instead of the project's own maintainers, because the reviewer-suggestion service derives the roulette key from the URL slug (client-go) while the project was registered under gitlab-api-client-go. In the discussion on contributors-gitlab-com!2736 we agreed to rename the key to client-go everywhere instead of adding an override mapping.
Companion MR (www-gitlab-com rename of projects.yml and team member files): gitlab-com/www-gitlab-com!144178 (merged)
Merge ordering
This MR and the companion rename MR should merge close together: while one side still says gitlab-api-client-go and the other says client-go, this project's Danger reviewer roulette silently stops matching its maintainers. Suggested order: the www-gitlab-com MR first, this one immediately after.