-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Describe the issue
At Arch Linux, we are trying to integrate Weblate into the ALPM project for streamlining the translation process. We have created the Weblate project at https://hosted.weblate.org/projects/alpm with a single component for now.
Our workflow will be:
GitLab push → Weblate auto-updates → translators edit in Weblate → Weblate pushes to MR branch → GitLab Merge Request
So we have created a checklist for setting this up.
However, on our infrastructure side, pushing from Weblate fails with "Could not push alpm/alpm: GitLab merge request API access for gitlab.archlinux.org is not configured". According to the docs, we need to set up the GITLAB_CREDENTIALS configuration to be able to use self-hosted instances and we suspect that's the reason. I couldn't find that option on our dashboard and assumed that this should be done on your side somehow...
Can you clarify if our planned workflow if compatible with Weblate and why we might be experiencing that issue? We really appreciate if you could give us some pointers on how to fix this.
cc @dvzrv @christian-heusel @klausenbusk
I already tried
- I've read and searched the documentation.
- I've searched for similar filed issues in this repository.
Steps to reproduce the behavior
Follow the steps defined here and see the error:
Could not push alpm/alpm: GitLab merge request API access for gitlab.archlinux.org is not configured
Expected behavior
Successful sync between our self-hosted GitLab project and Weblate.
Screenshots
No response
Exception traceback
How do you run Weblate?
weblate.org service
Weblate versions
No response
Weblate deploy checks
Additional context
No response