See previous requests at T248547: Run emptyUserGroup on the beta cluster (again) and T241504: Run emptyUserGroup on the beta cluster
Identified on beta enwiki:
- test1 https://en.wikipedia.beta.wmflabs.org/wiki/Special:UserRights/Et15
- test2 https://en.wikipedia.beta.wmflabs.org/wiki/Special:UserRights/Et15
Identified on beta commonswiki
- extended-uploader https://commons.wikimedia.beta.wmflabs.org/wiki/Special:ListUsers?group=extended-uploader
- importer https://commons.wikimedia.beta.wmflabs.org/wiki/Special:UserRights/Ori.livneh
- importers https://commons.wikimedia.beta.wmflabs.org/wiki/Special:UserRights/Ori.livneh
Note that import is the correct group name
mwscript emptyUserGroup.php --wiki=enwiki test1 mwscript emptyUserGroup.php --wiki=enwiki test2 mwscript emptyUserGroup.php --wiki=commonswiki extended-uploader mwscript emptyUserGroup.php --wiki=commonswiki importer mwscript emptyUserGroup.php --wiki=commonswiki importers
Additionally, https://en.wikipedia.beta.wmflabs.org/wiki/Special:UserRights/Reviewer includes the --force group. Testing locally, it appears that, with the current emptyUserGroup expecting the group name to be an unnamed argument, it is impossible to specify that --force is the name of the group, rather than a parameter being passed to the script. As a result, as far as I can tell the only way to remove the group is manually updating the user groups via eval.php
mwscript eval.php --wiki=enwiki $u = User::newFromName( 'Reviewer' ); $u->removeGroup( '--force' );
Yes, User::removeGroup is deprecated, but its easier to use here than to try and interact with the services needed directly.