-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
Allow to use self-hosted gitlab instances with own CA cert chain #869
Comments
Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️ |
Hey, thanks for reporting! The possible solution you recommended looks solid, would you be down to implement it? 🐻 I can also try it out but it would be easier if you already have an environment to test it out. |
Sorry missed your answer. Sadly I have no experience with rust yet and therefore I don't think I can provide a good PR :-( |
I am encountering the same issue. Any chance for this to be implemented soon? |
Now implemented in #1021, it's going to be the part of the release that I'm planning to push tomorrow. Testing it would be appreciated! |
Is there an existing issue for this?
Description of the bug
Hi,
currently it's not possible to use git-cliff with a self-hosted GitLab instance that uses an own CA for example with self-signed certificates.
A possible solution would be to use the
rustls-tls-native-roots
feature instead ofrustls-tls
for reqwest or provide a similar CLI argument like uv in astral-sh/uv#2362Steps To Reproduce
Expected behavior
git-cliff can request information from a self-hosted GitLab instance using an own CA cert chain
Screenshots / Logs
Software information
Additional context
No response
The text was updated successfully, but these errors were encountered: