Prevent Weblate from creating commits about weblate HOT 8 OPEN

See https://docs.weblate.org/en/latest/admin/continuous.html#lazy-commits for info when Weblate commits. #8770 will make commits happen less often.

from weblate.

This issue has been marked as a question by a Weblate team member. Why? Because it belongs more to the professional Weblate Care or community Discussions than here. We strive to answer these reasonably fast here, too, but purchasing the support subscription is more responsible and faster for your business. And it makes Weblate stronger as well. Thanks!

In case your question is already answered, making a donation is the right way to say thank you!

from weblate.

Can I disable Lazy Commits? I really want full control over when Weblate commits, and there are many events that I do not control:

• Somebody else changes an already changed string.
• A merge from upstream occurs (as far as I can tell, Weblate updates from upstream constantly)
• A file download is requested.

Alternatively: I can blow away merge conflicts by calling wlc reset. I'm concerned that also blows away database changes that have been made in the mean time. Or will those be written out again to the fresh set of files merged from upstream?

from weblate.

Disabling lazy commits would make Weblate immediately commit each change. We had that in the very beginning, and you would rather not use that.

Somebody else changes an already changed string.

#8770 will address this.

A merge from upstream occurs (as far as I can tell, Weblate updates from upstream constantly)

If you configure a webhook, it does, but you can choose not to configure it and update manually.

A file download is requested.

This is currently being discussed at #11256

I'm concerned that also blows away database changes that have been made in the mean time. Or will those be written out again to the fresh set of files merged from upstream?

Reset does discard all changes on Weblate side.

from weblate.

Disabling lazy commits would make Weblate immediately commit each change.

I apologize for using the wrong terminology. I meant to say disable automatic committing altogether.

Let me take a step back: for unclear reasons, Weblate occasionally behaves unreliably. Wrapping settings are not applied, some strings are marked "read-only" in some language for a reason I don't understand, keys in YAML objects are reordered, the order of headers in a gettext file are constantly changed, which was leading to conflicts. We've tried to solve this by heavily relying on scripting to normalize file contents, but this leads to more conflicts when Weblate is creating commits based on an outdated view of the world.

How would you suggest we best avoid merge conflicts?

from weblate.

I think the best approach would be to address the individual issues you encounter:

Wrapping settings are not applied

This is #11032 or something different?

some strings are marked "read-only" in some language for a reason I don't understand

Usually happens when source string is marked as needing editing.

keys in YAML objects are reordered

Weblate should keep existing ordering and add new strings to the end of the file. There is #11134 to make it match the ordering in the template for monolingual files.

the order of headers in a gettext file are constantly changed

The ordering is currently hard-coded in translate-toolkit (library we use for manipulating with the files): https://github.com/translate/translate/blob/4a51a2aa7749b09ff77d74cd55111f8b0307dcc5/translate/storage/poheader.py#L112-L127 It should match what GNU gettext produces. If not, please file an issue there.

from weblate.

Bugs will always exist and new ones may be introduced; relying on them all to be fixed to unblock our workflow seems unrealistic.

But you are saying there is no other way, correct?

from weblate.

#8770 is the way to go. But it's not an immediate solution, fixing bugs could be faster.

from weblate.