In our current setup we let Weblate create a PR against our repository. This creates constant rebase/merge conflicts as we use a plugin to squash changes into one commit to prevent our git history being filled with many translations commits.
To resolve this we need to switch to a pull approach, where a GitHub Action pulls latest translations from Weblate on a weekly basis. This will allow us to decouple the repository from the Weblate copy and remove the squash commits plugin.
In our current setup we let Weblate create a PR against our repository. This creates constant rebase/merge conflicts as we use a plugin to squash changes into one commit to prevent our git history being filled with many translations commits.
To resolve this we need to switch to a pull approach, where a GitHub Action pulls latest translations from Weblate on a weekly basis. This will allow us to decouple the repository from the Weblate copy and remove the squash commits plugin.