Hi all,
I'm in the process of configuring a self-hosted instance of Weblate and
could use some input.
Our usage scenario:
* The aim is having Weblate commit translation updates directly to the
git repository of our project ("upstream").
* To keep the commit history reasonably clean we want to limit the
amount of commits performed by Weblate to about one commit per
translator per week
(it's likely translators won't work in parallel on a single
translation file most of the time)
* Ideally the upstream repository should be automatically pulled
(triggered via webhook)
The problem:
* It seems Weblate commits pending translation updates whenever the
upstream repository is pulled (regardless of the setting for "Age of
changes to commit").
* As our upstream repository updates quite often this results in much
more commits being made then intended and asked for by the "Age of
changes to commit" setting.
* A performed commit seems to also trigger a push in this scenario if
"Push on commit" is set (therefore ruling out the combination of
webhook and "push on commit")
* As this will still result in a lot of commits in Weblate's local
repository it won't be viable to commit them directly to the
upstream repository but would require some kind of manual squashing.
My question is therefore if it is possible to prevent commits on
repository updates? If translation changes were kept until "Age of
changes to commit" was reached this would be the ideal case for us.
Unfortunately in the current setup "lazy commits" [1] don't seem to be
lazy at all...
Are there alternative approaches to achieve our goal?
Best Regards and thanks in advance,
Patrick
[1] https://docs.weblate.org/en/latest/admin/continuous.html#lazy-commits
_______________________________________________
Weblate mailing list
[email protected]
https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
