Make Weblate Commit Before We Run Update Translations Commits

[johnzhou721]

Describe the bug

Reporting as bug not enhancement here since there's a bunch of noop commits updating the pot date in this repo and this will GUARANTEE to happen anytime you get new translations and ANYTHING changes upstream -- much more often than website.

From beeware/beeware.github.io#676

This is a frequent cause of translation lockups -- people modify the content, and an Update Translations commit gets pushed to sync the po file. However, the deleted strings are moved all the way to the end, and if people translates the string that gets modified and those changes are still pending commit from Weblate, it'd cause a conflict since the strings they changed has now went into the unknown.

Steps to reproduce

None so far. Weblate isn't setup yet.

Expected behavior

Make Weblate Commit Before We Run Update Translations Commits, make Weblate pull after we Update Translations if nessacary as well.

Screenshots

No response

Environment

Irrelevant

Logs

No response

Additional context

Refs beeware/beeware.github.io#686 for solution for website -- something similar is needed for tutorial.

[freakboy3742]

John: once again, you're jumping into a project you're not involved in, and providing help that hasn't been asked for, that isn't actually helping.

We are aware of this issue. This repo is still in the early stages of development. We're working on a wide range of translation related issues right now. That's why beeware-tutorial isn't the "live" tutorial yet.

Having formally logged issues for problems we're in the middle of solving doesn't actually help us work down our todo list any faster.

Closing this issue on that basis.

[johnzhou721]

We are aware of this issue. This repo is still in the early stages of development. We're working on a wide range of translation related issues right now. That's why beeware-tutorial isn't the "live" tutorial yet.

Thanks for letting me know about the status of this repo, was a bit confused because actual issues about the tutorial text are getting reported on this repo instead (see #2), so I thought it'd be the formal production one, didn't check tutorial.beeware.org.