Open deepaklor opened 6 years ago
Sorry you are having troubles. This puppet module hasn’t been maintained for several years. I recommend moving to a different module.
On Fri, Sep 14, 2018 at 03:49 deepaklor notifications@github.com wrote:
gitlab merge requests email sent with a hyperlink (view in github) is having a port appended and the hyperlink doesnt work until the port is manually removed on the URL .
Any idea How does merge request work on gitlab and send email.
which configuration file it uses and how it is appending an extra port number which is not required.
i could see the port number being used in the gitlab.yml .
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/spuder/puppet-gitlab/issues/164, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOyzviHB06ZBXD9mjCZ54hQNNAZ37olks5ua3uygaJpZM4Wo9rh .
which puppet module please you are referring to? what i am referring is what configuration can avoid the port on the merge requests email on gitlab. i am using gitlab omnibus, i was not very sure on the port used on the gitlab.yml file. is any visibility to the port in gitlab.yml file under external url section please.
See the readme here for information on the new recommended module. https://github.com/spuder/puppet-gitlab
I'm not sure what configuration gitlab needs for email. The people here may know gitlab.slack.com
Alright i am using omnibus which is supported i believe. Thank you for your comments
gitlab merge requests email sent with a hyperlink (view in github) is having a port appended and the hyperlink doesnt work until the port is manually removed on the URL .
Any idea How does merge request work on gitlab and send email.
which configuration file it uses and how it is appending an extra port number which is not required.
i could see the port number being used in the gitlab.yml .