-
-
Notifications
You must be signed in to change notification settings - Fork 959
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 without forking repo #4285
Comments
The option is already there, just set the push branch. See https://docs.weblate.org/en/latest/admin/continuous.html#push-changes |
This issue looks like a support question. We try to answer these reasonably fast, but in case you are looking for faster resolution, please consider purchasing support subscription and make Weblate stronger. |
Following the instructions for Github at https://docs.weblate.org/en/latest/admin/continuous.html#push-changes Weblate 4.1.1, Docker Image Weblate is throwing this error when the manual push button is tapped or I add a different translations language which triggers a local commit. : Also the local branch is develop instead of If I set the git |
Can you please enable verbose logging of VCS operations to see which of the operations did fail? Changing LOGGING in settings.py: "weblate.vcs": {"handlers": [DEFAULT_LOG], "level": "DEBUG"}, |
i have the same problem |
I will try later this week again with the log level for vcs. |
Another option is to configure Sentry integration. It would collect such errors with more details. |
The push URL might have to be set in some cases. Issue #4285
Thank you for your report, the issue you have reported has just been fixed.
|
Is your feature request related to a problem? Please describe.
Gitlab pipelines from merge requests.
Weblate create merge request, gitlab trigger pipeline, but pipeline fail because different repo without required settings (gitlab ci variables).
Describe the solution you'd like
I completely understand why Weblate fork repo. Translator don't need commit permissions to original repo, but still can propose changes. Well known workflow eg. on public github.
But this solution is problematic for us, mainly because of problem described above.
Proposal is to add possibility (settings in project, component, special vcs type gitlab-nofork ... not sure - for us it's not problem to configure it globally) to create branch in original repo.
Our workflow is "everyone" (internal developers) can commit to repository and maintainers merge proposed changes to protected branches.
The text was updated successfully, but these errors were encountered: