-
-
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
Resolve conflict in weblate #8328
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! |
UPDATEJust ran the
|
Just replace |
Thank you for your report; the issue you have reported has just been fixed.
|
Thanks @nijel, replacing |
Describe the issue
Set up a new component with Github and set up
qa
branch to fetch source strings from.After a few changes to the
qa
branch by the developers, weblate locks the component with a conflict errorAfter following the steps mentioned in Typical workflow for fixing merge conflicts, Git is giving the following error
error: Could not read 2dcb03a7d34b7a366cc0102fbc4c92542e7a5ca2
on running thegit remote update weblate
commandI 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
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: