This is just a helper repository for exchanging the data between the the Weblate online tool and the main Agama GitHub repository. It works like a buffer to avoid too frequent updates, it allows to send multiple small changes at once in a bigger batch.
If you want to contribute see the CONTRIBUTING.md file, for more details see the Agama internationalization documentation.
When a conflict happens in Weblate during pushing the changes to GitHub then the Weblate repository gets locked and does not accept any changes in the translations. This should avoid creating even more conflicts or wasting translators work for translating outdated messages.
To unlock the Weblate repository the conflicts need to be resolved.
You can merge the changes from the Weblate Git manually and resolve the conflicts from command line.
# clone this repository
git clone [email protected]:agama-project/agama-weblate.git
cd agama-weblate
# add the Weblate remote for each Weblate translation component,
# see the note below about the credentials
git remote add weblate-agama-web 'https://<user>:<api_key>@l10n.opensuse.org/git/agama/agama-web'
git remote add weblate-agama-service 'https://<user>:<api_key>@l10n.opensuse.org/git/agama/agama-service-master'
git remote add weblate-agama-products 'https://<user>:<api_key>@l10n.opensuse.org/git/agama/agama-products-master'
# fetch the remotes
git remote update weblate-agama-web
git remote update weblate-agama-service
git remote update weblate-agama-products
# merge the remotes
git merge weblate-agama-web/master
git merge weblate-agama-service/master
git merge weblate-agama-products/master
# now resolve the conflicts
git status
vim ...
git add ...
git commit
# after pushing the changes Weblate should automatically detect the resolved
# conflicts and it should unlock the locked translation project
git push
Your user name and the API key for the Weblate Git remote can be found at the Weblate account settings page at https://l10n.opensuse.org/accounts/profile/#api.
Alternatively you can reset the Weblate changes and re-read the GitHub repository from scratch. But because this might cause losing some translations it should be used with caution.
You need the admin permissions in the Weblate repository for this. Go to the
respective translation component and use the Manage
->
Repository maintenance
menu option. Then press the Reset
button in the
danger zone section.