-
-
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
3 way merge driver usage #9328
Comments
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
It is installed in |
So, it is used by default for all repos, and no additional configuration is required? Because if I change dir to an actual repo and check settings, it's not there:
|
Yes, it is used. All commands in Weblate are executed with |
I see, thank you for the explanation! |
The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.
|
Describe the issue
Hi.
I've been looking for ways to reduce merge conflicts.
This issue and this file came up.
I can't find any documentation about it.
The comment in the file says that it's installed for all weblate internal repositories. What are "internal repositories"? Just Weblate's local copies of upstream, or something else? I checked git config in weblate container, and the setting is not there.
Is it already used in my installation, and I just don't know about it? Or it specifically needs to be enabled? If so, can it be enabled globally for all repos?
I already tried
Steps to reproduce the behavior
Expected behavior
No response
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: