Standreas

> it is a runtime dependency - and we should re-open and retitle or open a new bug about. > .... > so it would be cool if we could...

As for the latest 2 now: `CONFLICT (add/add): Merge conflict in src/translations/obconf-qt_et.desktop.yaml` I think this happens when a new translation file is created and weblate pushes it immediately (as empty...

> Hmm, how can it avoid commits that add and modify a file to appear in the same pull request? Hitting "commit" in weblate's project does a force-push so it...

My understanding is that "There are uncommitted changes" means there are in the database but not yet in weblate repos. Not sure but I think weblate commits those on rebasing...

Just btw: I think there is still no webhook configured for immediately rebase weblate repos, this is done still by cron once every 24h afaik.

As said, setting up a webhook immediately rebases weblate's internal repo on every change in the main repo. https://docs.weblate.org/en/latest/api.html#post--hooks-github-

> .... first three commits for Estonian should already be squashed by Weblate, but that is not the case. Weblate bug/missing feature? As it happened again in obconf-qt just now...

The last 3 were somehow my fault, I didn't commit all in weblate before merging, thought he was done. It happens mostly when new language files are created ( weblate...

Actually weblate should/could be upgraded, but I'm somehow hesitant still. No idea if things would change. Anyway I'll turn always to my method to commit all before merging.

I activated backups some days ago, finally, shut down and made a first one.