On WFC we recently set a hard limit on group requests to be no more than 3 people in a group, even when requests are recursive/chained together. It got me thinking, now that this is a bit simpler, could we maybe delegate it to the bot to handle it?
Tentatively, I imagine it would be a (possibly permissioned? So that run hosts have to approve requests) command of the format /groupadd name one - name two. Output should be as follows:
- If neither name is already in a group: it should create a group for them
- if one of them is already in a group, check a configurable group size limit and, if passed, add the other one to that group
- if both are already in a group, check the group size limit. If the check passes, emit a warning that this action would merge the groups, to allow the executor to confirm (although our do-not-group request system was abolished recently, there may be other edge cases where a merge would be bad). If confirmed with /groupadd confirm, proceed to merge groups
(note that the first case does not check the configurable group size limit. I think if someone wants to disable grouping by setting the limit to 1 or 0, they should instead have a different configuration option to do so, for the sake of everyone's sanity.)
On WFC we recently set a hard limit on group requests to be no more than 3 people in a group, even when requests are recursive/chained together. It got me thinking, now that this is a bit simpler, could we maybe delegate it to the bot to handle it?
Tentatively, I imagine it would be a (possibly permissioned? So that run hosts have to approve requests) command of the format /groupadd name one - name two. Output should be as follows:
(note that the first case does not check the configurable group size limit. I think if someone wants to disable grouping by setting the limit to 1 or 0, they should instead have a different configuration option to do so, for the sake of everyone's sanity.)