-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Backend for self-hosted Gitlab still queries gitlab.com #7168
Comments
Probably the issue happens when calling Indeed if you add |
You're right, it looks like the API roots are hard-wired into decap-cms-lib-util. And setting the branch in my YAML do the trick, thanks a lot! 🥳 Should I create a PR to pass an optional |
@JbIPS a PR would be helpful, thanks! |
In case of a self-hosted Gitlab, the API request to get the default branch always call gitlab.com. This commit allow to pass a custom API root from the config to the API call. Fix decaporg#7168
In case of a self-hosted Gitlab, the API request to get the default branch always call gitlab.com. This commit allow to pass a custom API root from the config to the API call. Fix #7168 Co-authored-by: Martin Jagodic <[email protected]>
In case of a self-hosted Gitlab, the API request to get the default branch always call gitlab.com. This commit allow to pass a custom API root from the config to the API call. Fix #7168 Co-authored-by: Martin Jagodic <[email protected]>
Describe the bug
I configured a backend for my hosted version of Gitlab
On login:
GET https://gitlab.*****/api/v4/projects/web%2Flanding
✔️GET https://gitlab.com/api/v4/projects/web%2Flanding
❌Of course the 3rd call gives a 404 and login workflow stops.
I looked at the sources but couldn't find a static ref to
gitlab.com
.To Reproduce
Expected behavior
No call should be made to
gitlab.com
Screenshots
Applicable Versions:
CMS configuration
The text was updated successfully, but these errors were encountered: