You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the experience of setting up Mattermost + GitLab integration:
https://docs.gitlab.com/ee/integration/mattermost/ oauth redirect is not the same which is required by this plugin. However, gitlab documentation is linked even from official mattermost webpages as a recommended tutorial.
Self hosted (same network) instance of the gitlab has in default set Allow requests to the local network from webhooks and integrations to False; however, this option has to be set to True or Mattermost site has to be mentioned in the list there. in mygitlab.example.com/admin/application_settings/network -- it would be nice to mention this in the README
When setting calling /gitlab setup the wizard is providing hint in the form of links to the README. However, it appeared to me, that the links refs (the think behind #) is pointing to some older version of the README file. I can not confirm this, since I managed to configure everything and I am not willing to break it in order to find the message. 😄
The text was updated successfully, but these errors were encountered:
@wiggin77 - I haven't made updates there since 2021, so my memory is fuzzy on how to do so. I imagine we could submit PRs against their docs repo? @nab-77 and/or @mgdelacroix may also have some knowledge here.
From the experience of setting up Mattermost + GitLab integration:
Allow requests to the local network from webhooks and integrations
toFalse
; however, this option has to be set to True or Mattermost site has to be mentioned in the list there. inmygitlab.example.com/admin/application_settings/network
-- it would be nice to mention this in the README/gitlab setup
the wizard is providing hint in the form of links to the README. However, it appeared to me, that the linksrefs
(the think behind#
) is pointing to some older version of the README file. I can not confirm this, since I managed to configure everything and I am not willing to break it in order to find the message. 😄The text was updated successfully, but these errors were encountered: