-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitlab merge requests email sent with a hyperlink (view in github) is having a port appended #164
Comments
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 ***@***.***> 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
<#164>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOyzviHB06ZBXD9mjCZ54hQNNAZ37olks5ua3uygaJpZM4Wo9rh>
.
|
which puppet module please you are referring to? |
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 .
The text was updated successfully, but these errors were encountered: