mattermost / mattermost/mattermost-plugin-gitlab

Unable to add a subscription to any project inside a group

Open
#336 1 comment 0 reactions 1 assignee View on GitHub

@raghavaggarwal2308 is already working on this.

Since Sep 2, 2024.

Awaiting Submitter Action
Dominant language
JavaScript
Stars
152
Forks
97
Avg merge
1d 14h
Merged PRs (30d)
8

Description

I have Mattermost Team Edition Version: 7.5.1 and GitLab Community Edition [15.5.4] self-hosted both and the latest for today.
Got several projects at GitLab combined into a group.
Using genuine guide from [Readme.md](https://mattermost.gitbook.io/plugin-gitlab/setup/configuration).
Everything is fine up to Step 4 and there:
If I'm using `/gitlab subscriptions add thegroup issues,merges,pushes,pipeline,tag ` the group is connected. I don't need to connect the group, because I cannot assign webhook to it since I'm non-premium GitLab user.
So, if I'm trying to connect any of my projects by `/gitlab subscriptions add thegroup/theproject issues,merges,pushes,pipeline,tag ` - I'm getting an error 'Resource with such path is not found.' from the GitLab bot. I tried to start over with different Gitlab accounts, projects etc. - every time I cannot connect a project which is inside a group.

So the steps to reproduce will be:
1. Install Mattermost Team Edition Version: 7.5.1 and GitLab Community Edition [15.5.4]
2. Create three projects in Gitlab project{1,2,3}, and group them into 'mygroup'
3. Install mattermost-plugin-gitlab
4. Configure it precisely following the [instruction](https://mattermost.gitbook.io/plugin-gitlab/setup/configuration) up to step 4
5. Execute `/gitlab subscriptions add mygroup/project1 issues,merges,pushes,pipeline,tag` or `/gitlab subscriptions add mygroup/project1`
6. The error - is a denial from GitLab bot "Resource with such path is not found."

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.