-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
feat: gitUrl global option #11221
feat: gitUrl global option #11221
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do not misuse hostrules. A better solution would to try to use ssh url if no http use is provided by gitlab. And if it's also not provided use old fallback.
Add a global admin option to force ssh if both are available.
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
…randau/renovate into add-gitlab-hostrule-option-to-use-ssh
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a small issue
🎉 This PR is included in version 26.4.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes:
Added
gitUrl
as a global admin option. (as proposed in #5406 (comment)) Possible values:default
(or undefined) behaviour, which is to use http_url_to_repossh
, uses ssh_url_to_repo as URL for Gitendpoint
, which means ignore those URLs and use the configured endpoint directlyContext:
Cloning over SSH does not work (closes #5406)
Allow bot admins to override the default resolution for git remote, e.g. to switch GitLab from HTTPS to SSH-based. (closes #9708)
Renovate stalling with self-hosted GitLab with git over HTTP #8488
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: