Add ability for top-level group owners to ban members from the group
Implements backend for https://gitlab.com/gitlab-org/modelops/anti-abuse/team-tasks/-/issues/155
What does this MR do and why?
As part of "Git abuse rate limit" feature, this MR adds backend implementation to add the ability for top-level group owners to manually ban group members from the UI.
Previously, banning was only done automatically when group members exceeded the set limit for unique project downloads via UI or git clone.
Why is the implementation split into BE and FE MRs?
This MR included both FE and BE changes initially. However, during review, it was brought up that this might result in the FE changes being visible to some users (in this case the ban
option, but clicking on it wouldn't work) while the BE changes gets deployed.
Screenshots or screen recordings
See !108762 (merged) for the demo of this feature enhancement.
How to set up and validate locally
See !108762 (merged) for instructions on how to validate this feature enhancement.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.