mattermost-plugin-gitlab
mattermost-plugin-gitlab copied to clipboard
Recursively subscribe to subgroups
With https://github.com/mattermost/mattermost-plugin-gitlab/pull/125, the user can now subscribe to sub-groups using:
/gitlab subscribe parent-group/sub-group/sub-group-project
and
/gitlab subscribe parent-group/sub-group
However, subscribing to parent-group does not receive updates for any projects under parent-group/sub-group.
The task here is to be able to use a wildcard * to subscribe to multiple groups/projects at once.
/gitlab subscribe parent-group/sub-group/sub-group-project: onlysub-group-projectevents/gitlab subscribe parent-group/sub-group: onlysub-groupevents/gitlab subscribe parent-group/*: all sub-groups events/gitlab subscribe parent-group/sub-group/*: all sub-group-projects events/gitlab subscribe parent-group/**/*: all sub-group-projects in all sub-groups events
Maybe we can add ** to subscribe to all sub-projects?
Example :
/gitlab subscribe parent-group/sub-group/sub-group-project: onlysub-group-projectevents/gitlab subscribe parent-group/sub-group: onlysub-groupevents/gitlab subscribe parent-group/*: all sub-groups events/gitlab subscribe parent-group/sub-group/*: all sub-group-projects events/gitlab subscribe parent-group/**/*: all sub-group-projects in all sub-groups events
@manland Sounds good to me, though can you explain the difference between a group's events and all of its projects' events? Namely the difference between /gitlab subscribe parent-group/sub-group and gitlab subscribe parent-group/sub-group/*
@mickmister I don't often use groups but what I know it's related to issues. If you create an issue on a group it's not the same as creating issue in a project inside a group. So if I listen sub-group I will receive creating issue in it. But listening sub-group/* I will receive event only for a new issue in a sub-project
Closing due to inactivity. The issue can be reopened with more interest from our community.